chore: babysit merge-train/fairies-v5 CI (public_authwit_transfer failure)#23903
Closed
AztecBot wants to merge 1 commit into
Closed
chore: babysit merge-train/fairies-v5 CI (public_authwit_transfer failure)#23903AztecBot wants to merge 1 commit into
AztecBot wants to merge 1 commit into
Conversation
Empty commit to re-run CI and determine whether the public_authwit_transfer e2e failure (operator account signing_public_key note not found during entrypoint) is a flaky note-sync race or a deterministic regression.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Babysit/iteration PR for the
merge-train/fairies-v5CI failure (re: #23881).Failing test
cli-wallet/test/flows/public_authwit_transfer.sh— the only failing test on #23881; rest of CI is green.Root cause (so far)
During
aztec-wallet send transfer_in_public -f operator, the operator account'sentrypointreads its own signing key:i.e. the operator account's
signing_public_key(aPrivateImmutable, written atdeploy-accountand discovered via tagging with the account's own address) is not present in the operator PXE's note DB at simulation time.Bisection
cicheck was green on this flow.v5-nexthas not advanced since the merge.This points to a note-sync timing issue (fresh-account own-note race), possibly exposed by the #23827 mempool/sequencer changes, rather than a logic bug in the #23785 NoteStore refactor.
This PR
Empty re-trigger commit to get a clean CI signal on the same merged content and confirm whether the failure is flaky or deterministic, and to provide a branch to land a fix on. No source changes yet.
Created by claudebox · group:
slackbot