Bone Meal only works in Creative

Testing out the mod for a server, i noticed that Bone Meal doesn't work in survival mode. When trying to use it in survival, it causes the villager anger particles to show up, and does nothing. It works perfectly fine in creative though, but it has no cooldown there.

Me using a Bone Meal hoe in survival

Me using it again, but in creative

Hello, you Need to have bone meal in your inventory for it to work in
survival (to balance it out).
On Wed, Apr 10, 2024, 18:46 BlueIsADude @.***> wrote:

Testing out the mod for a server, i noticed that Bone Meal doesn't work in
survival mode. When trying to use it in survival, it causes the villager
anger particles to show up, and does nothing. It works perfectly fine in
creative though, but it has no cooldown there.
image.png (view on web)
https://github.com/alessandrv/alessandrv-enchantments/assets/159506207/de8a54a6-e1cf-4c16-a77b-bb253e9908d8
Me using a Bone Meal hoe in survival
image.png (view on web)
https://github.com/alessandrv/alessandrv-enchantments/assets/159506207/6b7b2321-eb4d-4baf-a5af-36758dfb935f
Me using it again, but in creative
—
Reply to this email directly, view it on GitHub
https://github.com/alessandrv/alessandrv-enchantments/issues/14, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A4CF43G3OEDCT2F7WWDQUXLY4V3GXAVCNFSM6AAAAABGA4IJF6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZTMMJSGQZTEMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

ohhhhhhhhh ok
that makes sense lol, but maybe you could specify that in the enchantment description?


Create ContractWrapper for GasPriceMinimum

Expected Behavior
A wrapper should exist in contractkit for GasPriceMinimum.
Current Behavior
It does not currently exist, and #475 is blocked. The mobile app needs to be able to estimate gas and relies on this contract to do so. Until this wrapper exists, walletkit can't be removed from the mobile app.

I have a beginning for this at #1041, but it only has few methods to access data that is needed for that PR

I see one exists. closing this


ingress gateway not routing the request to service

Bug Description
Hi Support,
i have a service called admin-portal and i am putting a VS and GW to pass through the istio ingressgateway and the DNS i am using is "portal.dev.expressplay.com". However, i am getting the below error
GET / HTTP/1.1" 503 NC cluster_not_found
Full error:
[2022-09-12T07:55:37.414Z] "GET / HTTP/1.1" 503 NC cluster_not_found - "-" 0 0 0 - "<IP_ADDRESS>,<IP_ADDRESS>" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36" "feca4e51-4480-9aa0-8f2d-8170f6d4c1c3" "portal.dev.expressplay.com" "-" - - <IP_ADDRESS>:8443 <IP_ADDRESS>:52941 - -
Below are my config Files:
GW yaml:
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: admin-portal
  namespace: intr-dev
spec:
  selector:
    istio: ingressgateway
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - portal.dev.expressplay.com
    - portal.xpressplay.net
    - portaltest.dev.expressplay.com
    tls:
      httpsRedirect: true
  - port:
      number: 443
      name: https
      protocol: HTTP
    hosts:
    - portal.dev.expressplay.com
    - portal.xpressplay.net
    - portaltest.dev.expressplay.com

VS yaml:
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: admin-portal
  namespace: intr-dev
spec:
  hosts:
  - "portal.dev.expressplay.com"
  - "portal.xpressplay.net"
  - "portaltest.dev.expressplay.com"
  gateways:
  - admin-portal
  http:
  - route:
    - destination:
        host: admin-portal.intr-dev.svc.cluster.local
        port:
          number: 8080

Service yaml
kind: Service
apiVersion: v1
metadata:
  name: admin-portal
  namespace: intr-dev
  labels:
    app: admin-portal
spec:
  ports:
  - name: http
    port: 8080
  selector:
    app: admin-portal

Can you please help resolve this issue?
Regards,
Pranav
Version
pnateri@C02G70NAMD6M ~ % istioctl version
client version: 1.14.0
control plane version: 1.14.0
data plane version: 1.14.0 (16 proxies)

pnateri@C02G70NAMD6M ~ % kubectl version --short
Client Version: v1.21.2-13+d2965f0db10712
Server Version: v1.21.14-eks-6d3986b

Additional Information
bug-report.tar.gz
please find the attached bug report

you can close this ticket. I learnt from the bug report that the issue was with the duplicate VS and GW in default namespace as well along with intr-dev.
Deleting them fixed the issue. No issues with my configuration
Regards,
Pranav

close as not issue


Bugs documentation

The readme suggests that the library contains bug, could you document them in issues so that can be visible and get to by someone who has the time.
Thanks

Thank you for posting.
OK, let's clarify as much as possible.

I updated the README.
Is there any other unclear point?

Everything is clear, thanks a lot.
On Firestore model and DataSource, one way to handle would be to use firestore's DocumentSnapshot to manage various operations. That could save time and prevent reimplementation.
just a thought

Everything is clear.
I think one way would be to use DocumentSnapshot as a service that can handle Firestore operations. That way we don't have to reimplement services that is offered by SDK.
Just a thought


add ticMinStep to y axis on charts (dev)

@cgettings, I added this to the axisY config for both the trend and the links chart (just in case, there). Renders fine for counts, and larger rates. Think we need to do anything else here?

@mmontesanonyc can't think of anything else. As long as it actually works, let's roll with it.


Interrupt options different, irritating

SICStus has
Prolog interrupt options:
    a        abort           - cause abort
    b        break           - cause break
    c        continue        - do nothing
    e        exit            - cause exit
    d        debug           - start leaping
    z        zip             - start zipping
    t        trace           - start creeping
    h        help            - get this list

whereas Trealla has
Action or (h)elp: h
Action (#digit), (e)nd, e(x)it, (r)etry, (c)ontinue, (t)race, cree(p):

In particular the e option is completely irritating. Is should rather be a like abort. And the real exit should be e and not x

Also in SWI:
Options:
a:           abort         b:           break
c:           continue      e:           exit
g:           goals         s:           C-backtrace
t:           trace         p:		  Show PID
h (?):       help


f80 low level format check

update the GUI to reflect low level format time (not 8H) + audit the secure erase code

functioning correctly, logs are in /mnt/store0/log/boot_* for the specific date/time
hexdump of a drive shows data is all 000`s and correctly wiped the data.


Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object

Description
I'm getting these error in all the ubuntu runners (Including the self hosted ones)

Below is the Error i'm getting since yesterday.
error pulling image configuration: download failed after attempts=1: error parsing HTTP 403 response body: invalid character '<' looking for beginning of value: "<?xml version='1.0' encoding='UTF-8'?><Error>AccessDenied<Message>Access denied.</Message>Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object. Permission 'storage.objects.get' denied on resource (or it may not exist).</Error>"
Could you please help me out
Note: GCP creds are authenticating sucessfully andgcloud auth configure-docker is also going without any error.
Only the docker pull is throwing the error. In This Action
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[x] GitHub Actions - Larger Runners

Runner images affected

[X] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
runs-on: ubuntu-22.04
Is it regression?
no
Expected behavior
Should/Must build or pull the image succesfully...
Actual behavior

See the above image for more details
Repro steps

will have a look.
(from the first glance looks like "something happened on gcloud side")

Nope @ilia-shipitsin
It was previously running fine on my self hoster runner.
And from today afternoon self hosted runner is getting the same PROB
Guessing the issue is with image.

sure, I keep in mind docker version change (I really wonder what else could trigger 403).
can you please provide repro steps in text, not screenshot ?
if that repo is public, link to repo would be fine as well.

Repo is PRIVATE
Sorry can't able to give it.
Sure here are the steps
`
build:
name: Build and Push Image
runs-on: self-hosted
needs: [run-tests]
steps:
- uses: actions/checkout@v2
- id: 'auth'
  uses: 'google-github-actions/auth@v1'
  with:
    credentials_json: '${{ secrets.GKE_KEY }}'

# Setup gcloud CLI
- uses: google-github-actions/setup-gcloud@v1
  # with:
    # version: '390.0.0'
    # service_account_key: ${{ secrets.GKE_KEY }}

# Configure docker to use the gcloud command-line tool as a credential helper
- run: |
    # Set up docker to authenticate
    # via gcloud command-line tool.
    gcloud auth configure-docker
    gcloud info

# Build the Docker image
- name: Build and Push
  run: |
    IMAGE=gcr.io/***-152302/*****
    BRANCH=`echo $GITHUB_REF | sed -e 's/refs\/heads\///g'`
    TAG=$BRANCH-${GITHUB_SHA:0:7}-$(date +%s)

    docker build -t $IMAGE:$TAG -f Dockerfile .
    docker push $IMAGE:$TAG
    docker tag $IMAGE:$TAG $IMAGE:$BRANCH
    docker push $IMAGE:$BRANCH
    if [[ $BRANCH = "master" ]]; then
      docker tag $IMAGE:$TAG $IMAGE:latest
      docker push $IMAGE:latest
    fi

`

@ilia-shipitsin
Tried all these
 # Set up docker to authenticate
        # via gcloud command-line tool.
        sudo apt update
        #gcloud auth login
        #gcloud auth application-default login
        gcloud auth configure-docker
        gcloud info
        echo =======================================
        #gcloud auth list
        #gcloud projects list
        #gcloud config set account `Asyncro`
        #gcloud components install docker-credential-gcr
        #docker-credential-gcr configure-docker
        echo ========================================
        docker --version
        echo $GKE_KEY
        #echo $HOME/.docker/config.json
        cat $HOME/.docker/config.json
        #gcloud auth activate-service-account --key-file $HOME/.docker/config.json

NEED help ASAP
Development is stopped for last 2 days..

well, I'm on it.
current image deployed (not working):
https://github.com/actions/runner-images/blob/releases/ubuntu22/20230517/images/linux/Ubuntu2204-Readme.md
previous image (working):
https://github.com/actions/runner-images/blob/releases/ubuntu22/20230507/images/linux/Ubuntu2204-Readme.md
can you please have a look ? from my point of view, there's google sdk version change (I do not see other related changes, but I might be wrong). Does it help if you downgrade google sdk (is it possible from command line ?)
thank for the repro, I need to get gcp access, it will take time

Well,
tried pretty much

Ubuntu 20.4
Ubuntu 22.4
Ubuntu 18.4
Ubuntu LTS

ETC....
does not helping

I tried to install google sdk (the one from previous version), but it is not avaiable anymore
        run: |
          sudo apt-get update -y
          sudo apt-get install -y google-cloud-sdk=429.0.0

E: Version '429.0.0' for 'google-cloud-sdk' was not found

GOOGLE SDK version is not an issue.
I narrowed it down.
@ilia-shipitsin

GOOGLE SDK version is not an issue. I narrowed it down. @ilia-shipitsin

I really wonder what was the cause.
from you repro only google sdk and docker engine are involved

wait.
what is google sdk version on self hosted agent(s) ?

just a wild guess, may gcloud init help ?
https://stackoverflow.com/questions/56302658/anonymous-caller-does-not-have-storage-objects-get

wait. what is google sdk version on self hosted agent(s) ?

In both self hosted and in Ubuntu runner images
433.xx.xx

I recall similar weird issues from my past experience with kaniko (and artifactory as container storage). In that solution workaround was really weird, i.e. disabling reproducible builds.
I won't be surprised if we will end with something like that.
please give me some time (I need to setup GCE access and try things)

Okay,
No worries
Thanks

Could you recommend me any other runner image, Other then Ubuntu for this ?

@codeArtisanry
I was able to build and push docker image to GCR
https://github.com/ilia-shipitsin/gh7659/actions/runs/5182588796/jobs/9339542222
workflow: https://github.com/ilia-shipitsin/gh7659/blob/main/.github/workflows/blank.yml
seems, github actions is ok, hope we can close this issue

Thanks @ilia-shipitsin
You can close it now.
Just had to know, can you suggest to me what was the issue??
It can now run in Ubuntu 22.04 too.
Much appreciated your help.

well, it looked like "either something with image" or "something with GCE".
maybe you hit some GCE rate limit (but it is highly unlikely since your requests are authenticated)
ok, I'm closing this issue. feel free to reopen if needed

Thanks @ilia-shipitsin


sshtunnel/helm: use correct custom flag to enable/disable helm tunnel (fix)

Please update changelog.

Do we need to do that if there is no task related to PR? Or it isn't so?

Please update changelog.

Do we need to do that if there is no task related to PR? Or it isn't so?

I've noticed that there is linked task #1865.

@to-bar there is no need for adding changelog because this is the first time we release that feature. :+1::innocent:

@to-bar there is no need for adding changelog because this is the first time we release that feature. 👍😇

OK, so then I approve.


⚠ Processors has degraded performance

In a3598b1, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 139 ms

Resolved: Processors performance has improved in 8cad266.


Saving custom data associated with a car part

There is no current way to store data associated to custom car parts. Some hacks can be used to store certain data types but is very limited. The idea is being able to store all sort of data and as much as you want associated with an object.
The implementation would work as the following:

You enable the store data property on the Part class. This will attach a new component into the Part prefab.
You will have access to an ExpandoObject (Or just an string,object dictionary) through the Part, you will be able to store all your data here.
On game save SPL will loop through every CarProperties on the game and look up for the ones that have the SPL saving component. If they have it SPL will save the ExpandoObject as JSON and associate the data with the ObjectNumber from the CarProperties.
On game load (1 frame after game finished loading) SPL will load the JSON file and then loop through all existing CarProperties. If the CarProperties ObjectNumber does have data associated to it SPL will load it.

This might have some troubles to implement.

Modloader "Save" callback is called before the game is actually saved. A new callback has to be created that is called after game is saved.
There might be some issues with serialization of custom data types.

This will be worked on after SPL gets proper documentation.

Added in spl-1.4 branch.


real-time

Hello. congrats on the awesome work. I was just wondering whether we can use the model to do real time noise cancellation?

Hi @msaad1311,
Right now the model uses a very long window of ~1second, which would affect the real time application. An alternative might be to use shorter window lengths. Further optimizations are also possible like reducing the number of layers, filter length, number of filters per layer, etc.. Finally, it will also depend on your hardware and you might need further optimizations there, which I am not an expert at.


Revert the odd robotic garbling of our changelog ("Prep for 0.11.4 release")

This reverts commit f3e31744e24431a9f112db0d32ca96179000c623.

This isn't correct either. I'm updating.

I got the version but not the +## [unreleased] - unreleased.  Where are you updating what?

Still off. I got the rest @killerswan

Actually easier if you get...

Extran unreleased section after 0.11.4
and extra empty Added and Changed under 0.11.4

I thought you were in this repo rather than your own when you did everything. The release script and instructions assume you are working in a clone of the ponyc repo.

This pull request is just so we can catch the two or three errors that a revert would introduce that I'd have just pushed to ponylang/master without opening.


Fix: Cached AccessToken missing realm property in OIDC scenario

In the case an application is using a separate OIDC-compliant authority and the tid claim is empty, the cached access token does not contain a realm property. One side-effect is that the cached access token will fail the isAccessTokenEntity check, preventing it from being re-used.

@microsoft-github-policy-service agree [company="Dialexa, an IBM Company"]

@microsoft-github-policy-service agree company="Dialexa, an IBM Company"

@tnorling addressed comment and added a test. The beachball command reported no change files are needed.

@tnorling addressed comment and added a test. The beachball command reported no change files are needed.

Ah I suspect this is because your feature branch is also called dev. Can you try another branch?

@tnorling addressed comment and added a test. The beachball command reported no change files are needed.

Ah I suspect this is because your feature branch is also called dev. Can you try another branch?

Good call! Sorry for the messy commits, but I got the change files in place!

@tnorling Hello! Is there anything I can do to help this land?

@bbush915 I can help land this. Looks like some tests are failing.

@sameerag I validated that tests are all passing locally. Is there anything I can do to troubleshoot the failing E2E tests? It looks like they are all reporting: Git fetch failed with exit code: 128

@tnorling @sameerag following up on the above, I'm not sure why the E2E tests are failing, but can do what is needed to assist. Hoping to get this to land soon, since it is blocking some upgrades.

Hey cool and awesome former co-workers 🙂! Can this get approved and merged? It's blocking a couple companies and their clients including one I'm working with 😅

Hey cool and awesome former colleagues 🙂! Can this get approved and merged? It's blocking a couple companies and their clients including one I'm helping with 😅🙏🏾. So sorry, for the push and hope I don't come off as rude!

Approved and updated the base branch. Hopefully tests pass now.

Hey cool and awesome former colleagues 🙂! Can this get approved and merged? It's blocking a couple companies and their clients including one I'm helping with 😅🙏🏾. So sorry, for the push and hope I don't come off as rude!

Approved and updated the base branch. Hopefully tests pass now.

 😭 🙏🏾 ❤


Add py.typed

We add the py.typed file to the package, so that the clients can use mypy with it.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.111%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
41

Relevant Lines:
45

💛  - Coveralls


[bug 910789] Redo sampledata and add api responses

This redoes how we generate sample data for feedback responses:

adds api responses based on the product
changes it to 100 happy + 100 sad + 1000 other responses
fixes it so we're looking at product tuples which group a product,
version, platform and useragent together -- previously we did
them separately which resulted in weirdo/impossible combinations
adjust the locale generator so it looks a bit more like typical
Input data

This might also fix problems with the smoketests.
r?

WFM. I still get the same smoke test error I usually get (test_date_filter). r+

I'll have to look into that. Maybe generating 1000 isn't enough. Maybe they need to be closer together datetime-wise.
7e6defd [bug 910789] Redo sampledata and add api responses
Thank you!


Add init.py to tests directory such that tests can be run by appveyor

This is an effort to address the issues being noted in appveyor when attempting to build the conda package
https://ci.appveyor.com/project/conda-forge/staged-recipes/builds/26444171

Thanks Lewis!  Duly merging your PR.
I don't think we need to update the version number in the top level setup.py to account for this, but note for future PRs that we typically do this with each change.

Thanks @davidraythompson I will need to wait for a new release before the conda-forge package can be built.


Bug 1894667: bump(k8s): Fix  bug in reflector not recovering from 'Too large resource version'

Similar to what we did with https://bugzilla.redhat.com/show_bug.cgi?id=1881068
/assign @bparees
in @adambkaplan 's absence
and with a question @bparees - since this upstream k8s bug was fixed in 19.0 and 20.0, and does not exist in 4.6 and 4.7, do we still have to go through the bugzilla propagation change, where I create "dummy" bz's for those releases, or can we override that part the process?

strictly speaking the process would be to create the bugs and let QE verify that the issue does not exist in 4.7 + 4.6 before we merged this fix.  but i will take you at your word :)

strictly speaking the process would be to create the bugs and let QE verify that the issue does not exist in 4.7 + 4.6 before we merged this fix. but i will take you at your word :)

thanks @bparees :-)

/assign @adambkaplan
in case you have pto cycles to approve
/assign @coreydaley
for lgtm
/assign @soltysh
in case you have cycles to approve while @adambkaplan is out

/lgtm


Suggestion : Replace hacky method to auto-close the cmd window

I have been looking into some way to compile GUI deno app to run on Windows with Tauri before, with great success but without making much FFI effort.
Here is what I have (found & made)
First simple method is to change a byte into the deno compile binary from Typescript after it's done.
the other method is directly a suggestion i have made in the denoland/deno repo that adds the -subsystem option in deno compile in order to select if you wish to bundle a GUI app or a console app (windows only)
From this issue https://github.com/denoland/deno/discussions/11638
// --allow-read --allow-write change_exe_subsystem.ts

async function readN(r: Deno.Reader, n: number): Promise<Uint8Array | null> {
  const buf = new Uint8Array(n);
  let nRead = 0;
  // a null value of r.read() will nullish coalesce into NaN and
  // polute nRead, causing (nRead < n) to be false and the loop to exit
  while (nRead < n) {
    nRead += await r.read(buf.subarray(nRead)) ?? NaN;
  }
  return isNaN(nRead) ? null : buf;
}

async function writeAll(w: Deno.Writer, buf: ArrayBufferView): Promise<void> {
  const bytes = new Uint8Array(buf.buffer, buf.byteOffset, buf.byteLength);
  let nWritten = 0;
  while (nWritten < bytes.byteLength) {
    nWritten += await w.write(bytes.subarray(nWritten));
  }
}

function view(buf: ArrayBufferView) {
  return new DataView(buf.buffer, buf.byteOffset, buf.byteLength);
}

// replace 'my_oak_server.exe' with your server binary
const PATH_TO_BINARY = "./my_oak_server.exe";
const bin = await Deno.open(PATH_TO_BINARY, { read: true, write: true });

// we're going to validate (loosely) that its a valid EXE/MZ
 // reset to index 0, just to be sure
await bin.seek(0, Deno.SeekMode.Start);
const magicBytes = await readN(bin, 2);
if (magicBytes == null) {
  console.log("Encountered EOF at magicBytes");
  Deno.exit(1);
}
const binMagic = new TextDecoder().decode(magicBytes);

if ("MZ" != binMagic) {
  console.log(`☹ we didnt find a valid exe at ${PATH_TO_BINARY}`);
  Deno.exit(1);
}

// we now know we have a valid exe file
// next we need to get the offset of the 'PE Header'
const PE_ADDRESS_OFFSET = 0x3C;
await bin.seek(PE_ADDRESS_OFFSET, Deno.SeekMode.Start);
// read the peHeaderPointer as 32bit little-endian int/dword/u32
const peHeaderPointerBytes = await readN(bin, 4);
if (peHeaderPointerBytes == null) {
  console.log("Encountered EOF at peHeaderPointerBytes");
  Deno.exit(1);
}
const peHeaderPointer = view(peHeaderPointerBytes).getUint32(0, true);

// we've got the offset of the PE header now
// we'll go to that offset, then a further 92 bytes
// this is where the subsytem field is
await bin.seek(peHeaderPointer + 92, Deno.SeekMode.Start);

// WINDOWS subsystem (don't show a terminal)
// CONSOLE subsystem (show a terminal when running)
const SUBSYSTEM_WINDOWS = 2;
const SUBSYSTEM_CONSOLE = 3;

// before we modify the value we'll do a very rough check
// to make sure that we are modifying the right field
// we'll need to get it as a little-endian u16
const subsystemBytes = await readN(bin, 2);
if (subsystemBytes == null) {
  console.log("Encountered EOF at subsystemBytes");
  Deno.exit(1);
}
const subsystem = view(subsystemBytes).getUint16(0, true);
if (!(SUBSYSTEM_WINDOWS == subsystem || SUBSYSTEM_CONSOLE == subsystem)) {
  console.log("Oops! The subsystem is not WINDOWS=2 or CONSOLE=3.");
  console.log("We might be editing the wrong field,");
  console.log("  _or_ the EXE uses a different subsystem.");
  Deno.exit(1);
}

// okay, now we are pretty sure about the file
// let's update its subsystem
const newSubsystemData = new Uint16Array(1);
view(newSubsystemData).setUint16(0, SUBSYSTEM_WINDOWS, true);
// go back to the subsytem field
await bin.seek(peHeaderPointer + 92, Deno.SeekMode.Start);
// write out our data.
await writeAll(bin, newSubsystemData);

// finish up with a helpful message
const newSubsystemValue = view(newSubsystemData).getUint16(0, true);
if (SUBSYSTEM_WINDOWS == newSubsystemValue) {
  console.log(`Done! Changed ${PATH_TO_BINARY} subsystem=2, WINDOWS.`);
}
else if (SUBSYSTEM_CONSOLE == newSubsystemValue) {
  console.log(`Done! Changed ${PATH_TO_BINARY} subsystem=3, CONSOLE.`);
}

And my suggestion to add directly to Deno :
https://github.com/denoland/deno/discussions/12941
Both are great, but I believe for Astrodon it can be easier to just not "close" the console and instead just make it a real GUI app (Windows will know the difference)
this is a suggestion, let me know what you think.

If it was added to deno itself, it would be awesome, I will try script your mentioned asap :)

Implemented on https://github.com/astrodon/astrodon/commit/2ce53e555ec974f3ab8f56d2931f2762ca4609d7


Increase trade query performance by indexing database columns

Current trade database is quite bare-bones. It is worth starting to index the frequently searched fields so we can improve these query response times.
Proposed indexes are:
station: arrival distance
latest_market_data: supply, demand, price

Current trade database is quite bare-bones. It is worth starting to index the frequently searched fields so we can improve these query response times.
Proposed indexes are: station: arrival distance latest_market_data: supply, demand, price

removing max_landing_pad_size from station indexes, cardinality is too low to be useful


⚠ Processors has degraded performance

In 7ea0c22, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 45 ms

Resolved: Processors performance has improved in 2da41cd.


Looking for Qt binding project

I like to show web content in a Qt application. This could be implemented with QWebEngineView, but increases the app size dramatically and links against all QtWebEngine* which requires to build/ship Qml/QtWebKit. I do not want to crossbuild QtWebEngine for Linux, macOS, mingw.
This webview looks very promising, but I miss the binding to Qt. Is there already a Qt-integration somewhere?
Thanks a lot!
What OS are you using (uname -a, or Windows version)?
linux, macOS, windows (mingw)
What programming language are you using (C/C++/Go/Rust)?
C/C++ 17
What did you expect to see and what you saw instead?

A small qml demo that will be optimized in the future


Limitations for YouTube command.

People can request for YouTube videos up to the integer limit, which will destroy my server, so I need to fix this ASAP, as soon as as get home.

Fixed.


Added rededge 1-3 as common names #19

Implements #19

So my use case is exactly "Awesome Spectral Indices". I'd like to apply a spectral index from the list to data and just get the correct assets (bands) from the metadata based on the common name (or wavelength, if no common name is present). This only works right now if the formula doesn't include a rededge1,2,3 band. The overlapping wavelengths (and CBNs) are an issue though.

S2 red bands are:

B05 | Vegetation red edge, 704.1 nm (S2A), 703.8 nm (S2B) | 20m
B06 | Vegetation red edge, 740.5 nm (S2A), 739.1 nm (S2B) | 20m
B07 | Vegetation red edge, 782.8 nm (S2A), 779.7 nm (S2B) | 20m

Meeting notes: Needs a broader discussion, but rededge1-3 are not consistent with e.g. nir08 etc so we may want to change then to e.g. regedge70, rededge75 etc (as proposed by Emmanuel above). For this it would also be useful to know how other satellites do it and which bands they have. So I'll look that up and propose a name.

Hey! Sorry to just jump into the discussion. @m-mohr opened and Issue in ASI (https://github.com/awesome-spectral-indices/awesome-spectral-indices/issues/30) (I just renamed it), and it would be cool to have the mapping from the ASI standard to this standard. So, just to give you an overview, the bands and their standard in ASI were selected according to bands required by specific spectral indices (a band in a specific index shouldn't be ambiguous). E.g., in the case of Sentinel-2, there are indices that require the three red edge bands (see IRECI = (RE3 - R) / (RE1 / RE2)) -> This index couldn't be computed if the red edge bands were just a common unique band.

Interesting resource: https://eoreader.readthedocs.io/en/v0.19.1/optical_band_mapping.html

@davemlz: What do you think about the current state? Is that something that would work for ASI?

Actually, I think we can merge this and update it during the beta if needed.

Wow! Thank your for this!
@m-mohr this looks perfect. I will update the mapping from ASI to eo ;)

https://github.com/awesome-spectral-indices/awesome-spectral-indices/commit/35d75efcecb49b016ba28c6df420200556e0a9f8 Done ;)


New feature: global -q "quiet" flag

It would be useful to have a global flag to make certain commands produce output in a format easy to parse by e.g. bash scripts.
That would allow scripting like
for ORG in $(cf -q orgs) ; do
  ...
done

Hi @dmcintyre-pivotal
We try to keep the CLI simple, so it can be easily used in scripting. Rather than building in to the CLI the power of bash commands, we encourage you to apply the bash commands to it.
E.g.:
for ORG in $(LANG=en-US cf orgs | sed  -e "1,/^name/d") ; do
  ...
done

Hi Dies,
I'm not suggesting "building the power of bash" into the CLI, I'm suggesting stripping the extraneous noise from the output so that it is easily parseable by scripts.
At the moment, for every command, it's necessary to work out the right combination of sed/grep/head/tail... to get at the actual information. Everyone who writes scripts has to reinvent this for themselves. It's bound to be error-prone.
wifi-5-27:cf-abacus dmcintyre$ cf spaces
Getting spaces in org dmcintyre as<EMAIL_ADDRESS>
name
trader
basic-demo
abacus
namespace

wifi-5-27:cf-abacus dmcintyre$ for ORG in $(LANG=en-US cf orgs | sed  -e "1,/^name/d") ; do
> echo $ORG
> done
demos
dmcintyre

OOPS!
But if we had
wifi-5-27:cf-abacus dmcintyre$ cf -q spaces
trader
basic-demo
abacus
namespace

There would be no problem.

#864 is suggesting basically the same, using as a switch whether we're in a non-tty session.

@dkoper Your suggestion doesn't account for colors that may be added to the output and is, I think, unreasonable.


fix: ExplorerActions overlapping with file name.

before:

after:

it's more friendly for reviewing if there are some screenshots 😄
the mb-8 looks more comfortable than mb-6


Amplify.auth: "Channel shutdown due to tls negotiation timeout" error, but only on mobile networks (works ok on wifi)

Describe the bug
I am writing a swiftui app using Amplify Auth/Cognito. I was able to get everything working well (Sign-up/Sign-in/Logout/etc...) until I tested it on a mobile network outside of my usual WIFI.
When on mobile networks I am getting a network error, however not only that my network is fine, also other network operations inside my app are working without any problem.
The error is:
"Channel shutdown due to tls negotiation timeout"
Steps To Reproduce
Steps to reproduce the behavior:
1. Use Amplify Authenticate in a Wifi environment - no problem, all works fine
2. Turn off wifi, open the app in the street while on mobile (5g) network - getting errors
3. One thing to note - I am in France, and I am using the us-east-1 server. However my fiber (and wifi) provider is the same as the one I am using for mobile.

Expected behavior
I expect everything to work as usual agnostic to what type of network I am using.
Maybe there's a restriction using a US based server from a carrier in Europe?
Amplify Framework Version
2.4.0
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5.7
CLI version
10.7.3
Xcode version
14.2 (14C18)
Relevant log output

Log Messages

**2023-03-20 12:33:41.316038+0100 my app [3920:1348453] [UserPoolSignInHelper]
Checking next step for:
signingInWithSRP(AWSCognitoAuthPlugin.SRPSignInState.error(AWSCognitoAuthPlugin.SignInError.service(error:
ClientRuntime.SdkError<AWSCognitoIdentityProvider.InitiateAuthOutputError>.client(ClientRuntime.ClientError.retryError(AwsCommonRuntimeKit.CRTError.crtError(AwsCommonRuntimeKit.AWSError(errorCode: 1067,
errorMessage: Optional("Channel shutdown due to tls negotiation timeout")))), nil))), ["password": "<REDACTED>", "username": "CC********************************21", "clientMetadata": [:],
 "signInMethod": AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.userSRP)])**

```
Is this a regression?
No
Regression additional context
No response
Device
iPhone 13 pro
iOS Version
16.2
Specific to simulators
No response
Additional context
No response

It seems that the requests are timing out due to a slow connection. To help us debug further, would you be able to provide the following?
Logs you see in the console when when this scenario happens. You can enable verbose logging to the console by doing this:
Amplify.Logging.logLevel = .verbose

Hi @harsh62
Here is the entire log:

Log Messages

2023-03-21 23:40:35.809123+0100 myApp[1056:176489] [Amplify] Configuring
2023-03-21 23:40:35.809146+0100 myApp[1056:176489] [Amplify] Configuration: nil
2023-03-21 23:40:35.817406+0100 myApp[1056:176489] [Amplify] Could not find Cognito Identity Pool configuration
2023-03-21 23:40:35.821930+0100 myApp[1056:176483] [AWSCognitoAuthPlugin] Credential Store state change:

notConfigured
Amplify configured with auth plugin
2023-03-21 23:40:35.822835+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.notConfigured" =     {
    };
}
2023-03-21 23:40:35.823392+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuth" =     {
    };
}
2023-03-21 23:40:35.823473+0100 myApp[1056:176489] [AWSAuthSignUpTask] Starting execution
2023-03-21 23:40:35.823759+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthConfiguration.swift Starting execution
2023-03-21 23:40:35.824218+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] Credential Store state change:

migratingLegacyStore
2023-03-21 23:40:35.824421+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/MigrateLegacyCredentialStore.swift Starting execution
2023-03-21 23:40:35.837491+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/MigrateLegacyCredentialStore.swift Sending event CredentialStoreEvent.loadCredentialStore
2023-03-21 23:40:35.837553+0100 myApp[1056:176481] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2023-03-21 23:40:35.837581+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2023-03-21 23:40:35.838010+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential amplifyCredentials
2023-03-21 23:40:35.846082+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2023-03-21 23:40:35.846130+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] No existing session found.
2023-03-21 23:40:35.846144+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2023-03-21 23:40:35.846146+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthConfiguration.swift Sending event AuthEvent.validateCredentialAndConfiguration
2023-03-21 23:40:35.846155+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2023-03-21 23:40:35.846324+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2023-03-21 23:40:35.846359+0100 myApp[1056:176489] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.validatingCredentialsAndConfiguration" =     {
    };
}
2023-03-21 23:40:35.846381+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ValidateCredentialsAndConfiguration.swift Starting execution
2023-03-21 23:40:35.846391+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ValidateCredentialsAndConfiguration.swift Sending event AuthEvent.configureAuthentication
2023-03-21 23:40:35.846478+0100 myApp[1056:176481] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/ori/Library/Developer/Xcode/DerivedData/My_App-dqcwjxvqgktfwudujmwbyrnfcybv/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2023-03-21 23:40:35.846494+0100 myApp[1056:176481] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2023-03-21 23:40:35.846503+0100 myApp[1056:176481] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2023-03-21 23:40:35.846560+0100 myApp[1056:176489] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuthentication" =     {
        "AuthenticationState.notConfigured" =         {
        };
    };
}
2023-03-21 23:40:35.846736+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthenticationConfiguration.swift Starting execution
2023-03-21 23:40:35.846771+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthenticationConfiguration.swift Sending event AuthenticationEvent.configure
2023-03-21 23:40:35.847471+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential deviceMetadata(username: "7D83FC92-851A-4901-847E-F1611CDDD658")
2023-03-21 23:40:35.847764+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuthentication" =     {
        "AuthenticationState.configured" =         {
        };
    };
}
2023-03-21 23:40:35.847792+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ConfigureAuthentication.swift Start execution
2023-03-21 23:40:35.847838+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ConfigureAuthentication.swift Sending event AuthenticationEvent.initializedSignedOut
2023-03-21 23:40:35.847908+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuthentication" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
    };
}
2023-03-21 23:40:35.848038+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ConfigureAuthentication.swift Sending event AuthEvent.authenticationConfigured
2023-03-21 23:40:35.848643+0100 myApp[1056:176481] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuthorization" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.notConfigured" =         {
        };
    };
}
2023-03-21 23:40:35.848690+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthorizationConfiguration.swift Starting execution
2023-03-21 23:40:35.848716+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeAuthorizationConfiguration.swift Sending event AuthorizationEvent.configure
2023-03-21 23:40:35.849770+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configuringAuthorization" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.configured" =         {
        };
    };
}
2023-03-21 23:40:35.849791+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ConfigureAuthorization.swift Starting execution
2023-03-21 23:40:35.849798+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/ConfigureAuthorization.swift Sending event AuthEvent.authorizationConfigured
2023-03-21 23:40:35.849933+0100 myApp[1056:176484] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.configured" =         {
        };
    };
}
2023-03-21 23:40:35.852168+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2023-03-21 23:40:35.852198+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/ori/Library/Developer/Xcode/DerivedData/My_App-dqcwjxvqgktfwudujmwbyrnfcybv/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2023-03-21 23:40:35.852288+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2023-03-21 23:40:35.852295+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2023-03-21 23:40:35.852308+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2023-03-21 23:40:35.852341+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2023-03-21 23:40:35.852348+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2023-03-21 23:40:35.852364+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential asfDeviceId(username: "7D83FC92-851A-4901-847E-F1611CDDD658")
2023-03-21 23:40:35.854118+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2023-03-21 23:40:35.854160+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2023-03-21 23:40:35.854163+0100 myApp[1056:176489] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/ori/Library/Developer/Xcode/DerivedData/My_App-dqcwjxvqgktfwudujmwbyrnfcybv/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/Keych2023-03-21 23:40:35.854166+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
ainStoreError.swift
function: recoverySuggestion
line: 69)
2023-03-21 23:40:35.854240+0100 myApp[1056:176489] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2023-03-21 23:40:35.854303+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StoreCredentials.swift Starting execution
2023-03-21 23:40:35.854304+0100 myApp[1056:176482] [AWSCognitoAuthPlugin] Credential Store state change:

storingCredentials
2023-03-21 23:40:35.893478+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StoreCredentials.swift Sending event CredentialStoreEvent.completedOperation
2023-03-21 23:40:35.893536+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2023-03-21 23:40:35.893544+0100 myApp[1056:176487] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2023-03-21 23:40:35.894318+0100 myApp[1056:176489] [AWSCognitoAuthPlugin] Credential Store state change:

success(AWSCognitoAuthPlugin.CredentialStoreData.asfDeviceId("626D2EB1-04F6-41D4-AB06-0FC1B87D4DA0", "7D83FC92-851A-4901-847E-F1611CDDD658"))
2023-03-21 23:40:35.894332+0100 myApp[1056:176489] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2023-03-21T23:40:35+0100 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 User-Agent: aws-sdk-swift/1.0 api/cognito-identity-provider/1.0 os/iOS/16.3.1 lang/swift/5.7 lib/amplify-ios/2.4.0,
x-amz-user-agent: aws-sdk-swift/1.0,
X-Amz-Target: AWSCognitoIdentityProviderService.SignUp,
Content-Type: application/x-amz-json-1.1,
Host: cognito-idp.us-east-1.amazonaws.com,
Content-Length: 6380
 Optional([])
2023-03-21T23:40:35+0100 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-idp.us-east-1.amazonaws.com/?")with max connections: 50

2023-03-21T23:41:06+0100 info SerialExecutor : [Logging] Connection to endpoint: Optional("https://cognito-idp.us-east-1.amazonaws.com/?") is closing
An error occurred while registering a user AuthError: The operation couldn’t be completed. (AwsCommonRuntimeKit.CRTError error 2.)
Recovery suggestion: Check your network connection, retry when the network is available.
HTTP Response stauts code: nil
Caused by:
network
2023-03-21 23:41:06.044943+0100 myApp[1056:176746] [AWSAuthSignInTask] Starting execution
2023-03-21 23:41:06.046871+0100 myApp[1056:176746] [AWSAuthTaskHelper] Check if authstate configured
2023-03-21 23:41:06.047039+0100 myApp[1056:176746] [AWSAuthTaskHelper] Auth state configured
2023-03-21 23:41:06.047089+0100 myApp[1056:176746] [AWSAuthSignInTask] Validating current state
2023-03-21 23:41:06.048748+0100 myApp[1056:176746] [AWSAuthSignInTask] Signing with userSRP
2023-03-21 23:41:06.048828+0100 myApp[1056:176746] [AWSAuthSignInTask] Sending signIn event
2023-03-21 23:41:06.049259+0100 myApp[1056:176746] [AWSAuthSignInTask] Waiting for signin to complete
2023-03-21 23:41:06.049415+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.notStarted" =             {
            };
        };
        "AuthorizationState.configured" =         {
        };
    };
}
2023-03-21 23:41:06.050112+0100 myApp[1056:176747] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IntializeSignInFlow.swift Starting execution
2023-03-21 23:41:06.050444+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2023-03-21 23:41:06.050511+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2023-03-21 23:41:06.050606+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential deviceMetadata(username: "7D83FC92-851A-4901-847E-F1611CDDD658")
2023-03-21 23:41:06.052826+0100 myApp[1056:176746] [UserPoolSignInHelper] Checking next step for: notStarted
2023-03-21 23:41:06.056795+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2023-03-21 23:41:06.057004+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2023-03-21 23:41:06.057003+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/ori/Library/Developer/Xcode/DerivedData/My_App-dqcwjxvqgktfwudujmwbyrnfcybv/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2023-03-21 23:41:06.057071+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2023-03-21 23:41:06.057149+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2023-03-21 23:41:06.075307+0100 myApp[1056:176746] [AWSCognitoAuthPlugin] No existing device metadata found. AuthEnvironment(configuration: AWSCognitoAuthPlugin.AuthConfiguration.userPools(["poolId": "us-e****fuOq", "hostedUI": "N/A", "pinpointAppId": "(nil)", "region": "<REDACTED>", "endpoint": "N/A", "clientId": "5d8v****eni0", "clientSecret": "c3****1f"]), userPoolConfigData: Optional(["poolId": "us-e****fuOq", "hostedUI": "N/A", "pinpointAppId": "(nil)", "region": "<REDACTED>", "endpoint": "N/A", "clientId": "5d8v****eni0", "clientSecret": "c3****1f"]), identityPoolConfigData: nil, authenticationEnvironment: Optional(AWSCognitoAuthPlugin.BasicAuthenticationEnvironment(srpSignInEnvironment: AWSCognitoAuthPlugin.BasicSRPSignInEnvironment(srpAuthEnvironment: AWSCognitoAuthPlugin.BasicSRPAuthEnvironment(userPoolConfiguration: ["poolId": "us-e****fuOq", "hostedUI": "N/A", "pinpointAppId": "(nil)", "region": "<REDACTED>", "endpoint": "N/A", "clientId": "5d8v****eni0", "clientSecret": "c3****1f"], cognitoUserPoolFactory: (Function), eventIDFactory: (Function), srpClientFactory: (Function), srpConfiguration: (nHexValue: "FFFFFFFFFFFFFFFFC90FDAA22168C234C4C6628B80DC1CD129024E088A67CC74020BBEA63B139B22514A08798E3404DDEF9519B3CD3A431B302B0A6DF25F14374FE1356D6D51C245E485B576625E7EC6F44C42E9A637ED6B0BFF5CB6F406B7EDEE386BFB5A899FA5AE9F24117C4B1FE649286651ECE45B3DC2007CB8A163BF0598DA48361C55D39A69163FA8FD24CF5F83655D23DCA3AD961C62F356208552BB9ED529077096966D670C354E4ABC9804F1746C08CA18217C32905E462E36CE3BE39E772C180E86039B2783A2EC07A28FB5C55DF06F4C52C9DE2BCBF6955817183995497CEA956AE515D2261898FA051015728E5A8AAAC42DAD33170D04507A33A85521ABDF1CBA64ECFB850458DBEF0A8AEA71575D060C7DB3970F85A6E1E4C7ABF5AE8CDB0933D71E8C94E04A25619DCEE3D2261AD2EE6BF12FFA06D98A0864D87602733EC86A64521F2B18177B200CBBE117577A615D6C770988C0BAD946E208E24FA074E5AB3143DB5BFCE0FD108E4B82D120A93AD2CAFFFFFFFFFFFFFFFF", gHexValue: "2"))), userPoolEnvironment: AWSCognitoAuthPlugin.BasicUserPoolEnvironment(userPoolConfiguration: ["poolId": "us-e****fuOq", "hostedUI": "N/A", "pinpointAppId": "(nil)", "region": "<REDACTED>", "endpoint": "N/A", "clientId": "5d8v****eni0", "clientSecret": "c3****1f"], cognitoUserPoolFactory: (Function), cognitoUserPoolASFFactory: (Function), cognitoUserPoolAnalyticsHandlerFactory: (Function)), hostedUIEnvironment: nil)), authorizationEnvironment: nil, credentialsClient: AWSCognitoAuthPlugin.CredentialStoreOperationClient, logger: Amplify.OSLogWrapper)
2023-03-21 23:41:06.075677+0100 myApp[1056:176746] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IntializeSignInFlow.swift Sending event SignInEvent.initiateSignInWithSRP
2023-03-21 23:41:06.077461+0100 myApp[1056:176747] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StartSRPFlow.swift Start execution
2023-03-21 23:41:06.077500+0100 myApp[1056:176747] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/StartSRPFlow.swift Sending event SignInEvent.initiateSignInWithSRP
2023-03-21 23:41:06.077738+0100 myApp[1056:176747] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Starting execution
2023-03-21 23:41:06.078369+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.signingInWithSRP" =             {
                "SRPSignInState.notStarted" =                 {
                };
                clientMetadata =                 {
                };
                password = "<REDACTED>";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.userSRP)";
                username = "7D********************************58";
            };
        };
        "AuthorizationState.configured" =         {
        };
    };
}
2023-03-21 23:41:06.078499+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.signingInWithSRP" =             {
                "SRPSignInState.initiatingSRPA" =                 {
                    clientMetadata =                     {
                    };
                    password = "<REDACTED>";
                    signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.userSRP)";
                    username = "7D********************************58";
                };
                clientMetadata =                 {
                };
                password = "<REDACTED>";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.userSRP)";
                username = "7D********************************58";
            };
        };
        "AuthorizationState.configured" =         {
        };
    };
}
2023-03-21 23:41:06.078885+0100 myApp[1056:176745] [UserPoolSignInHelper] Checking next step for: signingInWithSRP(AWSCognitoAuthPlugin.SRPSignInState.notStarted, ["signInMethod": AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.userSRP), "clientMetadata": [:], "username": "7D********************************58", "password": "<REDACTED>"])
2023-03-21 23:41:06.079136+0100 myApp[1056:176745] [UserPoolSignInHelper] Checking next step for: signingInWithSRP(AWSCognitoAuthPlugin.SRPSignInState.initiatingSRPA(["clientMetadata": [:], "username": "7D********************************58", "password": "<REDACTED>", "signInMethod": AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.userSRP)]), ["clientMetadata": [:], "username": "7D********************************58", "password": "<REDACTED>", "signInMethod": AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.userSRP)])
2023-03-21 23:41:06.084424+0100 myApp[1056:176747] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2023-03-21 23:41:06.084425+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2023-03-21 23:41:06.084450+0100 myApp[1056:176747] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential deviceMetadata(username: "7D83FC92-851A-4901-847E-F1611CDDD658")
2023-03-21 23:41:06.087206+0100 myApp[1056:176747] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.throwError
2023-03-21 23:41:06.087243+0100 myApp[1056:176747] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2023-03-21 23:41:06.087253+0100 myApp[1056:176747] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2023-03-21 23:41:06.087263+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] Credential Store state change:

error(KeychainStoreError: Unable to find the keychain item
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/ori/Library/Developer/Xcode/DerivedData/My_App-dqcwjxvqgktfwudujmwbyrnfcybv/SourcePackages/checkouts/amplify-swift/AmplifyPlugins/Core/AWSPluginsCore/Keychain/KeychainStoreError.swift
function: recoverySuggestion
line: 69)
2023-03-21 23:41:06.087283+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2023-03-21 23:41:06.087307+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Starting execution
2023-03-21 23:41:06.087314+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] Credential Store state change:

loadingStoredCredentials
2023-03-21 23:41:06.087329+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Retreiving credential asfDeviceId(username: "7D83FC92-851A-4901-847E-F1611CDDD658")
2023-03-21 23:41:06.089720+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/LoadCredentialStore.swift Sending event CredentialStoreEvent.completedOperation
2023-03-21 23:41:06.089759+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Starting execution
2023-03-21 23:41:06.089769+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/IdleCredentialStore.swift Sending event CredentialStoreEvent.moveToIdleState
2023-03-21 23:41:06.089790+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] Credential Store state change:

success(AWSCognitoAuthPlugin.CredentialStoreData.asfDeviceId("626D2EB1-04F6-41D4-AB06-0FC1B87D4DA0", "7D83FC92-851A-4901-847E-F1611CDDD658"))
2023-03-21 23:41:06.089807+0100 myApp[1056:176488] [AWSCognitoAuthPlugin] Credential Store state change:

idle
2023-03-21 23:41:06.091610+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Starting execution
2023-03-21T23:41:06+0100 info CognitoIdentityProviderClient : [Logging] Request: POST https:443
 Path: /
 x-amz-user-agent: aws-sdk-swift/1.0,
X-Amz-Target: AWSCognitoIdentityProviderService.InitiateAuth,
Content-Type: application/x-amz-json-1.1,
User-Agent: aws-sdk-swift/1.0 api/cognito-identity-provider/1.0 os/iOS/16.3.1 lang/swift/5.7 lib/amplify-ios/2.4.0,
Host: cognito-idp.us-east-1.amazonaws.com,
Content-Length: 6736
 Optional([])
2023-03-21T23:41:06+0100 info SerialExecutor : [Logging] Creating connection pool for Optional("https://cognito-idp.us-east-1.amazonaws.com/?")with max connections: 50
2023-03-21T23:41:36+0100 info SerialExecutor : [Logging] Connection to endpoint: Optional("https://cognito-idp.us-east-1.amazonaws.com/?") is closing
2023-03-21 23:41:36.237110+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitiateAuthSRP.swift Caught error client(ClientRuntime.ClientError.retryError(AwsCommonRuntimeKit.CRTError.crtError(AwsCommonRuntimeKit.AWSError(errorCode: 1067, errorMessage: Optional("Channel shutdown due to tls negotiation timeout")))), nil)
2023-03-21 23:41:36.241543+0100 myApp[1056:176745] [UserPoolSignInHelper] Checking next step for: signingInWithSRP(AWSCognitoAuthPlugin.SRPSignInState.error(AWSCognitoAuthPlugin.SignInError.service(error: ClientRuntime.SdkError<AWSCognitoIdentityProvider.InitiateAuthOutputError>.client(ClientRuntime.ClientError.retryError(AwsCommonRuntimeKit.CRTError.crtError(AwsCommonRuntimeKit.AWSError(errorCode: 1067, errorMessage: Optional("Channel shutdown due to tls negotiation timeout")))), nil))), ["signInMethod": AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.userSRP), "username": "7D********************************58", "password": "<REDACTED>", "clientMetadata": [:]])
2023-03-21 23:41:36.241567+0100 myApp[1056:177051] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signingIn" =         {
            "SignInState.signingInWithSRP" =             {
                "SRPSignInState.error" =                 {
                    Error = "AWSCognitoAuthPlugin.SignInError.service(error: ClientRuntime.SdkError<AWSCognitoIdentityProvider.InitiateAuthOutputError>.client(ClientRuntime.ClientError.retryError(AwsCommonRuntimeKit.CRTError.crtError(AwsCommonRuntimeKit.AWSError(errorCode: 1067, errorMessage: Optional(\"Channel shutdown due to tls negotiation timeout\")))), nil))";
                };
                clientMetadata =                 {
                };
                password = "<REDACTED>";
                signInMethod = "AWSCognitoAuthPlugin.SignInMethod.apiBased(AWSCognitoAuthPlugin.AuthFlowType.userSRP)";
                username = "7D********************************58";
            };
        };
        "AuthorizationState.configured" =         {
        };
    };
}
2023-03-21 23:41:36.244078+0100 myApp[1056:176745] [AWSAuthSignInTask] Wait for signIn to cancel
2023-03-21 23:41:36.244222+0100 myApp[1056:177051] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.configured" =         {
        };
    };
}
Sign in failed AuthError: The operation couldn’t be completed. (AwsCommonRuntimeKit.CRTError error 2.)
Recovery suggestion: Check your network connection, retry when the network is available.
HTTP Response stauts code: nil
Caused by:
network
2023-03-21 23:41:36.246629+0100 myApp[1056:177052] [AWSAuthFetchSessionTask] Starting execution
2023-03-21 23:41:36.246674+0100 myApp[1056:177052] [AWSAuthTaskHelper] Check if authstate configured
2023-03-21 23:41:36.246751+0100 myApp[1056:177052] [AWSAuthTaskHelper] Auth state configured
2023-03-21 23:41:36.248992+0100 myApp[1056:177052] [FetchAuthSessionOperationHelper] Fetching current state
2023-03-21 23:41:36.249037+0100 myApp[1056:177052] [FetchAuthSessionOperationHelper] No session found, fetching unauth session
2023-03-21 23:41:36.249281+0100 myApp[1056:177052] [FetchAuthSessionOperationHelper] Waiting for session to establish
2023-03-21 23:41:36.249440+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.fetchingUnAuthSession" =         {
            "FetchSessionState.notStarted" =             {
            };
        };
    };
}
2023-03-21 23:41:36.249582+0100 myApp[1056:177052] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeFetchUnAuthSession.swift Starting execution
2023-03-21 23:41:36.249666+0100 myApp[1056:177052] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InitializeFetchUnAuthSession.swift Sending event FetchAuthSessionEvent.throwError
2023-03-21 23:41:36.249935+0100 myApp[1056:177052] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InformSessionError.swift Starting execution
2023-03-21 23:41:36.250071+0100 myApp[1056:177052] [AWSCognitoAuthPlugin] AWSCognitoAuthPlugin/InformSessionError.swift Sending event AuthorizationEvent.receivedSessionError
2023-03-21 23:41:36.253112+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.fetchingUnAuthSession" =         {
            "FetchSessionState.error" =             {
                error = "AWSCognitoAuthPlugin.FetchSessionError.noIdentityPool";
            };
        };
    };
}
2023-03-21 23:41:36.254037+0100 myApp[1056:177053] [FetchAuthSessionOperationHelper] Received error - sessionError(AWSCognitoAuthPlugin.FetchSessionError.noIdentityPool, noCredentials)
2023-03-21 23:41:36.254961+0100 myApp[1056:176745] [AWSCognitoAuthPlugin] Auth state change:

{
    "AuthState.configured" =     {
        "AuthenticationState.signedOut" =         {
            lastKnownUserName = "(nil)";
        };
        "AuthorizationState.error" =         {
            Error = "AWSCognitoAuthPlugin.AuthorizationError.sessionError(AWSCognitoAuthPlugin.FetchSessionError.noIdentityPool, noCredentials)";
        };
    };
}
Fetch Unauthenticated session failed with error - AuthError: Unexpected error occurred with message: Unknown error occurred
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-swift/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't.
My_App/StoryViewModel.swift:72: Fatal error: Unexpectedly found nil while unwrapping an Optional value
2023-03-21 23:41:36.269754+0100 myApp[1056:176203] My_App/StoryViewModel.swift:72: Fatal error: Unexpectedly found nil while unwrapping an Optional value
My_App

```

Would you be able to share your the contents of your awsconfiguration.json file with sensitive information removed. Also if you can share the code snippet of your setup?

Thanks for all the effort thus far.
Bellow are the requested data. Just to remind again that everything works well on Wifi.... the problem is only when on a mobile network.....
awsconfiguration.json

{
    "auth": {
        "plugins": {
            "awsCognitoAuthPlugin": {
                "IdentityManager": {
                    "Default": {}
                },
                "CognitoUserPool": {
                    "Default": {
                        "PoolId": "us-east-1_cu*******",
                        "AppClientId": "*******",
                        "AppClientSecret": "***********",
                        "Region": "us-east-1"
                    }
                },
                "Auth": {
                    "Default": {
                        "authenticationFlowType": "USER_SRP_AUTH",
                    }
                }
            }
        }
    }
}

Code:
In the Initialisation I do:
 do {
            try Amplify.add(plugin: AWSCognitoAuthPlugin())
            //Amplify.Logging.logLevel = .verbose
            try Amplify.configure()
            print("Amplify configured with auth plugin")
        } catch {
            print("Failed to initialize Amplify with \(error)")
        }

Then for Signup for example I do:

@MainActor func signUp(username: String, password: String) async {

        do {
            let signUpResult = try await Amplify.Auth.signUp(
                username: username,
                password: password

            )
            if case let .confirmUser(deliveryDetails, _, userId) = signUpResult.nextStep {
                print("Delivery details \(String(describing: deliveryDetails)) for userId: \(String(describing: userId))")
            } else {
                print("SignUp Complete")
            }
        } catch let error as AuthError {
            print("An error occurred while registering a user \(error)")
            signupFail = true
            signupError = error.errorDescription
        } catch {
            print("Unexpected error: \(error)")
            signupFail = true
            signupError = error.localizedDescription
        }
    }

@oricoh I don't have an update on the issue other than IPv6 should not be an issue for Cognito. To investigate this further, would you be able to provide some more data regarding the request/responses using a (Charles Proxy, Proxyman)?
Also may be try this on another platform so that we know if the issue is also platform specific?
This would help us further isolate what the problem could be?
Also SDK employs https://en.wikipedia.org/wiki/Happy_Eyeballs to determine which IP version to use. It will attempt both a ipv4 and ipv6 connection simultaneously, and choose the one that is better.

@harsh62
I can't install Charles on this work computer.
I tried another platform, the problem persists on MacOS's terminal, A windows computer, Xcode's simulator and several devices.
In the meantime I switched to us-east-2 the problem only happens on us-East-1

Hey @oricoh. Sorry lost track of this issue. Following up to see if you figured out the problem? If not, were you able to debug it further or get more information?

I wouldn't close it because the issue isn't solved.

@oricoh I closed it because I didn't hear on the issue. If the issue still persists could I get the following details:

Would you be able to share how you setup us-east-2 and us-east-1. Would you be able to compare if Cognito was setup differently in the 2 regions you mentioned?
Would you be able try this in Amplify V1 which uses aws-sdk-ios. It would help us identify if the problem persists across different libraries. This would help narrow down our invesigation to just the library or service.

Hope to hear from you soon.

They are both setup exactly in the same way, we had to move our entire operation to us-east-2.  At this point we are not going to move back us-east-1 anymore, but the problem still exist as I tried with an older version of the app not about a week ago.

Would you be able to try running your older version of the App using Amplify V1?

We are preparing for launch and the team is over stretched at the moment. I will be happy to try in a couple of weeks.


MM-17331: Only searching when needed on users autocomplete

Summary
Only searching and debouncing when needed on users autocomplete. So now the
loading only happens when is really hiting the server, and do not hit the
server when add more text to a search that was giving 0 results.
Besides I removed the debouncePromise library because is no longer needed.
Ticket Link
MM-17331

@srkgupta actually, the debounce function was already there, I have removed the debouncePromise function, but not added any new one. Anyway, if we need to add tests to the debounce function, that should be at the mattermost-redux repository where it is defined.

The changes will be tested as part of the 5.16 Guest Account feature. Removing the QA Review label.


Add a Svelte store and a counter demo that uses it

fac20389134168323d6cb4e65c4c562037dfb1d6 fixes a tsc error during build. Not sure why CI didn't catch it?
The rest is just a simple custom store along with a Vite+Svelte default project tweaked to work with automerge-repo. I don't know if you ultimately want a demo for every frontend framework, but I think having the store at least is useful.

Thanks for this, a really useful contribution.
I have flagged a few things for review. If you can get them patched up I will run CI and look at getting this merged.

Added a README and did a yarn upgrade @automerge/automerge to pick up version 2.0.3 (which fixed #60).

Apologies, I forgot to press the “complete review” button earlier. Just the formatting to sort

@acurrieclark should be fixed now. I updated the project level repo as well.

Thanks for this. Really appreciate the docs too.

hi! when is this being published into npm?


Update CI to official release of 3.1.0

Before contributing, please read our contributing guidelines and code of conduct.
Overview
updates our CI to 3.1.0, from 3.1.0-preview1
Related Github Issue
Include a link to the related GitHub issue, if applicable
Testing
The agent includes a suite of unit and functional tests which should be used to
verify your changes don't break existing functionality. These tests will run with
Github Actions when a pull request is made. More details on running the tests locally can be found
here for our unit tests,
and here for our functional tests.
For most contributions it is strongly recommended to add additional tests which
exercise your changes.
Reviewer Checklist

[ ] Perform code review
[ ] Add performance label
[ ] Perform appropriate level of performance testing
[ ] Confirm all checks passed
[ ] Add version label prior to acceptance

The other Kayla likes this too! 😉


Missing device configuration: Oomi Color Strip

Checklist

[X] It is not in the configuration DB

[X] It was not merged recently or has a pending PR

Which device is missing?
Oomi Color Strip
Manufacturer ID
N/A
Product Type
N/A
Product ID
N/A
Firmware Version
No response
Is the device listed on the Z-Wave Alliance website?
https://products.z-wavealliance.org/products/2362?selectedFrequencyId=-1
Do you have a manual?
Attaching logs for the interview for Node 20.
zwave-js-ui-store.zip
Also, here is the manual.
Oomi ColorStrip manual - 2.pdf
This is a re badge of the Aeotec LED Strip... https://products.z-wavealliance.org/products/2498?selectedFrequencyId=-1. According to manufacturer support, it can be flashed with the EXE firmware to re badge as Aeotec. Firmware 1.02 is available for this.

@zwave-js-bot import config 2362 from zwa

Attaching logs for the interview for Node 20.
zwave-js-ui-store.zip

Can you try again please? Looks like the interview didn't succeed because some strange route management was going on and the stick was unresponsive.

Strange. I 'healed' the node, and same issue. I also went under log, and removed the current log files. I then do a test, and both log files show 22 bytes or so. However, when I select both files and download, it is a few MB. So maybe I dont know how to clear the logs properly or something? But figured if I trashed the file, it would write a new one and not be loaded with info.

I ended up using my Z-Stick 5 with the PC controller firmware updater to change the firmware to ZW121 v1.3. As this was a rebadge of the Aeon (Aeotec) LED Strip. Then I unpaired it from Z-Stick 5, repaired it with Vera Plus, and relearned the network via Z-Stick 7 and HA. Re-interviewed and it comes up fine now.


(feature) Add bolt plan new --puppet flag

This adds the flag --puppet to the bolt plan new command, which
instructs the command to generate a new Puppet language plan instead of
a YAML plans. The YAML plan is still default, and the plans themselves
are equivalent. This additionally move the plan new handler from the
CLI class into it's own PlanCreator class in order to separate
concerns.
!feature

'bolt plan new' now accepts '--puppet' flag to generate Puppet plan
The 'bolt plan new' command now accepts a '--puppet' flag to generate
a Puppet plan.

Still need to finish up testing.

CLA signed by all contributors.


DDLS-208: Update setting of Due Date for reports to account for Bank Holidays & Weekends

Purpose
Align the setting of the due date with Sirius by factoring in bank holidays and weekends ensuring that we don't account for these.
Fixes DDLS-208
Approach

Install the Carbon mixin business days package
Install PHP calendar extension in order to account for Easter bank holidays
Wrap package in service class and call in Entity class
Unit test updated logic

Learning
Any tips and tricks, blog posts or tools which helped you. Plus anything notable you've discovered about DigiDeps
Checklist

[x] I have performed a self-review of my own code
[ ] I have updated documentation (Confluence/ADR/tech debt doc) where relevant
[x] I have added tests to prove my work
[ ] The product team have approved these changes
[ ] I have checked my work for potential security issues and refered to the OWASP top 10

Frontend

[ ] I have run an in-browser accessibility test (e.g. WAVE, Lighthouse)
[ ] There are no deprecated CSS classes noted in the profiler
[ ] Translations are used and the profiler doesn't identify any missing
[ ] Any links or buttons added are screen reader friendly and contextually complete
[ ] If adding GA events, I have updated or checked the existing category or label values

Also, can you include a test that attempts to set a report, that would fall on a bankholiday. So we can confirm that it sets the next business day.

This is the package that Sirius use so thought it would be best to use the same one to align our due dates with them.
The 'gb-engwales' holiday is set, which merges 'gb-national' with additional bank holidays so that they're all accounted for.


Replace jQuery for Aegis JS in Monogatari's core.

Replacement is complete and working fine. Marking as done.


GROOVY-9974: extract generics connections: Closure vs SAM return type

https://issues.apache.org/jira/browse/GROOVY-9974

Merged. Thanks!


Dictionary paging button should disable if there is nothing to load

Navigation arrows buttons should disable if there is no more elements to load in that direсtion.

Was done with dbeaver/pro#1711


pod install

Installing Realm (0.93.2)
[!] /bin/bash -c
set -e
sh build.sh cocoapods-setup
core is not a symlink. Deleting...
Downloading dependency: core 0.89.6

xcode 6.3

@longxianlin is there anything in particular that's not working?

Closing due to insufficient information and lack of activity.

same issue


Appstudio update test-component-pac-uela

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-uela-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
11 seconds
init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
36 seconds
build-container

✅ Succeeded
20 seconds
inspect-image

✅ Succeeded
22 seconds
deprecated-base-image-check

✅ Succeeded
23 seconds
clair-scan

✅ Succeeded
57 seconds
clamav-scan

✅ Succeeded
16 seconds
sbom-json-check

✅ Succeeded
25 seconds
label-check

✅ Succeeded
8 seconds
show-sbom

✅ Succeeded
8 seconds
show-summary


Cuppa should not run hooks for skipped or pending tests

Currently Cuppa runs before and beforeEach hooks before a skipped or pending test and after and afterEach hooks after it. This is inefficient and can lead to unexpected test failures if any of the hooks happen to fail.

The current status of this issue is:

Since #82 has been merged, we skip beforeEach and afterEach hooks correctly.
We still always run before and after hooks.
Our behaviour currently matches Mocha's.


Update webhooks-reference-implementation.md

Under the subheading "Reliable but more complex model", the text reads: Updating a webhook is done using the AddListWebHookAsync method. I changed the method name to UpdateListWebHookAsync

Hi @samjudeh, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;


Set python recursion limit higher

This sets the recursion limit higher by default on KEVM definitions.
I've confirmed with Python3.11 that this fixes the various segfaults/crashes we had seen before. We still need to up the default Python version somehow, but that's another issue.
Related: https://github.com/runtimeverification/pyk/issues/286

I've confirmed with Python3.11 that this fixes the various segfaults/crashes

Is this related to segfaults? My understanding is that changing Python version already fixes that.

I believe that both are needed. Let me double-check.

On Python 3.11 without upping the recursion limit, loading a Kore term that a client gets back from RPC server:

So we need both.

Ah wait though, I didn't see that main already was upping the limit. Let me try my example with the limit main is already setting.
The limit in __main__.py is enough for my example. So I'll close this.

So we need both.

Not for fixing the segfault though. Probably you'd get the same RecursionError on any Python version, but the segfault AFAIK is only reproducible on 3.8.


Add the Session to the State Tutorial chapter

There's a tiny error in the tutorial chapter Add the Session to the State
should be
props.appProps.userHasAuthenticated(true);
instead of
props.userHasAuthenticated(true);

Hmmm I don't think it should be because we pass the appProps to the component in its props. You can check it out in our sample repo - https://github.com/AnomalyInnovations/serverless-stack-demo-client/blob/redirect-on-login/src/containers/Login.js#L26


Unresolved references in Telegram Bot API 7.2 update

The new Telegram Bot API 7.2 objects do not exist in the schema, but other objects reference them

Looks like this is caused by absence of description for these objects...

Looks like this is caused by absence of description for these objects...

Yes! We have already discussed this with the author. Would you like to do a PR?)

Yes! We have already discussed this with the author.

Any suggestions on fix?

Yes! We have already discussed this with the author.

Any suggestions on fix?

I'm not familiar with Rust much, so I didn't do it myself. The author suggests leaving an empty string in the absence of a description
Unfortunately, the documentation is poorly done(
I tried to write in @BotTalk chats / bot support, but I got no result...

I don't think I have time now to do a proper PR but for a dirty fix you can go to /src/extractor.rs, line 66 and prepend
else if select_any.peek().matches(&table) {
    State::GetObjectFields {
        name: elem,
        description: RawDescription::default(),
    }
}

before the 'else' block.

It looks like issue was fixed after they added descriptions to entities like BusinessLocation, `BusinessIntro, etc 😅

can confirm, it has been fixed since then. the issue might be closed

The issue might be closed

It might reoccur in the future, it's better to implement such case handling...


Rename WorkType to Format

Preserves the workType field name, aggregation name and query parameters in the API for backwards compatability.

https://buildkite.com/wellcomecollection/catalogue/builds/471#dbe986b2-2db6-4cbb-a551-db855f6fe947/94-1137


Do we need the API Reference page?

Seems a bit redundant given the left nav that we have, right?

IMO it is not redundant. There are many classes and methods that are not easily discoverable from the left nav. Backoff configuration, for example, can be found by linking from a method that supports backoff, but it is not listed anywhere else. In the future I would like to add search/filter functionality to the API Reference page to make it easier to use.

Hm -- OK, let's leave it for now. :)


Task13 Gowthami- Excel Vs Workbook

Data Table variables-Read And Write the data from one excel to another excel sheet. Find the differences between excel and workbook

@gowthamikudumula
Task13: changes verified


Build binaries for different Surelog revisions

This draft was made for testing different Surelog revision, because we started getting Out Of Memory error at that time during opentitian synth test. The issue has been solved, machine with more RAM is used for the failing job from then on.


add fix_error function

Sorry it took some time. I tested the function with the view and controller I have written by mistake and it seems to work well. Feedback would be appreciated!

@jenachoi okay you can attach this method to the form now, as both branches have been merged in.


Include pgpass file during CI run

Remove the hardcode for establishing database connection in the Session object and transition to using pgpass file solely for database authentication. Add a step to the CI workflow file, which includes a command to touch a pgpass file in the home folder and write the login credentials to the file.

I just noticed that including the pgpass file still does not fix the issue for the hardcoding of database name. This was what I found:

.pgpass does not define a default database. It only provides the passwords for a combination of hostname, database and username.

This means I still need to hardcode these values in order for the pgpass file to retrieve the right password to make the database connection.


Deserialize nullable with null value

When the type being deserialized has an empty string value it return de default value of the underlying type instead of null

Good point. Thank you. I'll merge it soon.

Published in 3.2.3. Thank you for your contribution.


Notifier isn't working when the project is running run as service

When I run the project as service in windows, the project create a child process, which runs in the context of the user with system token, but the notification is not shown.
I proved cloning node-notifier and ran it with psexec -i -s, that use system token but is shown in the user environment, but the notification is not seen
Specifications
Node 10.15.3
Node-notifier 7.0.1
Windows 10 Pro

I have the same problem too

I no longer have easy access to Windows. Any help with debugging, implementation, and QA would be greatly appreciated.

Any update regarding this issue?

I have the same issue, any update?

I am trying to launch notifications when I run the project as a servicem any update here?

@mikaelbr any update on this? I'm willing to help debug this if there is no solution yet.

What if I don't have access to log on information?


Lack of current selected network on main page

Probably the issue for redesign, not for the current prototype stage:

Also the narrowing of the visible width of the tables:


Schema Root Message Name Ignored by parquet-fromcsv

Describe the bug
Tabular data split into two parquet files, with the same schema, one produced with parquet-ccp-arrow, the other with parquet-rs.
When concatenating I get Error: General("inputs must have the same schema, [...]")
To Reproduce

pip install pyarrow
create csv

cat << EOF > in.csv
x,y
1,2
EOF

convert csv to parquet using python wrapper over parquet-cpp

# csv_to_parquet.py
import sys
from pyarrow import csv, parquet as pq
table = csv.read_csv(sys.argv[1])
pq.write_table(table, sys.argv[2])

python csv_to_parquet.py in.csv a.parquet

create schema file

cat << EOF > schema.txt
message schema {
  OPTIONAL INT64 x;
  OPTIONAL INT64 y;
}
EEE

convert csv to parquet using parquet-rs

parquet-fromcsv --schema schema.txt --input-file a.csv -h --output-file  b.parquet -w 2

concatenate these two files parquet-concat c.parquet {a,b}.parquet

Expected behavior
Files get concatenated, two rows.
Additional context
The only difference is the message name.
 GroupType {
     basic_info: BasicTypeInfo {
-        name: \"schema\",
+        name: \"arrow_schema\",
         repetition: None,
         converted_type: NONE,
         logical_type: None,

schemas
Metadata for file: a.parquet

version: 2
num of rows: 1
created by: parquet-cpp-arrow version 16.1.0
metadata:
  ARROW:schema: /////6gAAAAQAAAAAAAKAAwABgAFAAgACgAAAAABBAAMAAAACAAIAAAABAAIAAAABAAAAAIAAABEAAAABAAAANT///8AAAECEAAAABQAAAAEAAAAAAAAAAEAAAB5AAAAxP///wAAAAFAAAAAEAAUAAgABgAHAAwAAAAQABAAAAAAAAECEAAAABwAAAAEAAAAAAAAAAEAAAB4AAAACAAMAAgABwAIAAAAAAAAAUAAAAA=
message schema {
  OPTIONAL INT64 x;
  OPTIONAL INT64 y;
}

Metadata for file: b.parquet

version: 2
num of rows: 1
created by: parquet-rs version 51.0.0
metadata:
  ARROW:schema: /////6gAAAAQAAAAAAAKAAwACgAJAAQACgAAABAAAAAAAQQACAAIAAAABAAIAAAABAAAAAIAAABEAAAABAAAANT///8QAAAAGAAAAAAAAQIUAAAAxP///0AAAAAAAAABAAAAAAEAAAB5AAAAEAAUABAADgAPAAQAAAAIABAAAAAYAAAAIAAAAAAAAQIcAAAACAAMAAQACwAIAAAAQAAAAAAAAAEAAAAAAQAAAHgAAAA=
message arrow_schema {
  OPTIONAL INT64 x;
  OPTIONAL INT64 y;
}

I also tested with both files in writer version 1, with a mix of version 1 and 2. Same error.

I started commenting on #4799, but since it is closed, not sure it'll get noticed.

This is expected and not a bug, you're attempting to concatenate two parquet files with differing schema which is not supported.
As the schema are not the same, not only is it not clear what the output schema should be, but more fundamentally as the tool concatenates encoded data, we can't permit schema changes

Is this due to arrow_to_parquet_schema which always sets the group name to "arrow_schema"? It's used by the writer in parquet-fromcsv.
/// Convert arrow schema to parquet schema
pub fn arrow_to_parquet_schema(schema: &Schema) -> Result<SchemaDescriptor> {
    let fields = schema
        .fields()
        .iter()
        .map(|field| arrow_to_parquet_type(field).map(Arc::new))
        .collect::<Result<_>>()?;
    let group = Type::group_type_builder("arrow_schema")
        .with_fields(fields)
        .build()?;
    Ok(SchemaDescriptor::new(Arc::new(group)))
}

If this is the case, is it a viable solution to just add metadata from arrow_schema_from_string in parquet-fromcsv?

label_issue.py automatically added labels {'parquet'} from #5814


find_status

After the find status (search query, search options, ...) change the core will send find_status to the frontend. find_status provides information about the number of matches but also about the query stored in the core (this will allow to only store the query in the core and not in the frontend = future work).
I will also update the documentation to add find_status to the RPC commands after getting some feedback on this.

Right. That would require to store the old field values and then compare them with the new ones. Currently, for indicating that the status should be sent a flag is set (find_changed). I guess it would be possible to store the new field values instead of the boolean value and then use those to determine which ones should be sent. Though, I am not sure if that makes things too complicated?

A possible solution: afaict there are two scenarios under which this message is sent. The first is when the client is opening a find dialog or equivalent; in this case if we have existing find state we should send it all (including regex etc). The second case is when the user is doing some find action; in this case we should only be sending the result count etc.
Does this cover everything, or am I confused? (very possible I'm confused)

That could work. Will try it out.

Instead of having just a simple flag to track the find changes, I added enum FindStatusChange to determine whether only the number of matches or all find parameters should be sent.

Okay, I like that change. I think this is ready to go; my only thought right now is whether we have frontend support. Your xi-mac branch currently crashes core, because it's still sending 'search_dialog'. Would you like to put up a small PR in xi-mac that supports the new behaviour, or should I? We should also let other frontend maintainers know that the current find RPC is going to break.

I pushed my xi-mac changes to my branch and uncommented the highlight_find RPCs.

The last update fixes the stack overflow when text is deleted and find occurrences need to be updated. While fixing this I also noticed that find occurrences are not correctly updated when text is inserted. Also, the find update was only applied to the visible area and not the entire document (resulted in wrong number of matches).


image builds stuck in prod

Image builds appear to be stuck in production. I did not yet dig deeper.

I have a few of these as well, same on stage. It's not an image-builder issue though, composer keeps reporting them as running :/

We have heartbeats now to prevent this, right?

This was solved with osbuild/osbuild-composer#1523


bridge traefik_admin not created in Ubuntu WSL with Windows

traefik_admin        bridge    local
I had to create it manually via docker network create "traefik_admin"

@jujusb link this issue to the commit related to the changes we did to the traefik's docker-compose.yml


Sign Up

Once you have signed up via email, it takes you straight through to the Dashboard with nothing on it. Can we have something that says - "Thank you for signing up, please check your email to confirm your account"

Roe to send friendly message

Friendly Message:
Thank you for signing up - click "Create Event" to get started. Uou may need to confirm your email address, so please check your emails and spam.


fix: fix bugs for rebuilding and snapshot purge then add more test steps

Which issue(s) this PR fixes:

Issue longhorn/longhorn#7199
What this PR does / why we need it:
Special notes for your reviewer:
Additional documentation or context

LGTM

@shuo-wu Is it ready for review?

Merge first. @shuo-wu will continue investigating the errors.


Rivine logo and colorscheme

https://github.com/rivine/rivine-UI/commit/48a3d9a3274fc21d53e8e363adb96a0926617ea9


[New Devices]ESP32 C3 C2 support

Hi
Any change to add ESP32 C3 and C2 AT Firmware ?
Cheers
J J

We talking with Espressif, ESP support is planned for the near future.

Examples for a few Espressif adapters is now available. We are still working on them, more feature on the way.

THanks


Cant emulate node draining within 2 minutes

Hi,
I've try to run the mock on my spot server with aws-node-termination-handler and I successfully received the events coming from this mock.
However my problem is that the moment I've run the mock the pods on the spot terminate immediately and the cluster-autoscaler takes time to spin up a new spot so I left with downtime.
My question is how do I set up the mock to mark the spot as terminate and the termination-handler to move the pods prior to "evicting" them from the spot.
Is this how it will reflect on real termination? if so how should I configure the termination-handler to catch the event and drain only after spinning up the new pods?

You can setup a Pod Disruption Budget (PDB) on your pods which will ensure that a configured number are always running.  If a spot interruption notice is received, aws-node-termination-handler will attempt to cordon and drain the node but the PDB could stall the evictions if evicting would cause the pod count to drop below your configured threshold. But keep in mind that if the 2-minute window ends, your pods may be forced to be shutdown ungracefully since the instance itself will be automatically shutdown.
You can read more about Pod Disruption Budgets here: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/

Thank you for the explanation, I just set the PDB and indeed its not allowing the eviction on the pods.
However the cluster-autoscaler doesn't receive an event to scale the nodes and move the pods to the new one. I know this is question not related to here but since we are talking what would be the best approach to handle that?

@roeP the PDB is only going to prevent the eviction, you would need another mechanism to trigger a scale up since cluster-autoscaler will only scale up based on the "pending pods" metric.  You can over-provision your cluster to achieve no downtime when a node disappears. That is probably your best bet right now. Over provisioning involves scheduling a configurable amount of headroom via low priority pause-pods.  This will ensure that you have space available for pods on another node.
When you receive a spot interruption notice, the aws-node-termination-handler will try to evict and then your pods will get rescheduled on-top of the pause-pods that were over provisioned for you.
NOTE: the following functionality does not exist today and probably doesn't make sense to add:
The aws-node-termination-handler could have functionality added to look at the pods it is evicting and scale up the number of pods on the node that is being drained after it cordons the node. I'm not sure this would be very helpful though. If a node has not already been booted, it's unlikely to have a node be launched and the pods rescheduled within the 2 minute window, so the better solution is still over-provisioning the cluster.
Hope that helps
More info on cluster-overprovisioner:

https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#how-can-i-configure-overprovisioning-with-cluster-autoscaler
https://medium.com/scout24-engineering/cluster-overprovisiong-in-kubernetes-79433cb3ed0e

Thank you. That was helpful. Will try it