Skip to content

Conversation

@mverzilli
Copy link
Contributor

Fourth part of the series started with #19445.

This makes the PrivateEventStore work based on staged writes. With this, private events aren't written to persistent storage until PXE decides to commit the job.

@mverzilli mverzilli added the ci-no-fail-fast Sets NO_FAIL_FAST in the CI so the run is not aborted on the first failure label Jan 12, 2026
@mverzilli mverzilli changed the base branch from next to martin/staged-writes-in-tagging-stores January 12, 2026 09:48
@mverzilli mverzilli requested review from Thunkar, benesjan and nventuro and removed request for Thunkar, benesjan and nventuro January 12, 2026 10:15
Copy link
Contributor

@nventuro nventuro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I understand your point re. rollbacks, but other than that this looks good. It's sad that the event store is in poor state but thats' life I guess.

@mverzilli
Copy link
Contributor Author

I'm not sure I understand your point re. rollbacks, but other than that this looks good. It's sad that the event store is in poor state but thats' life I guess.

Good news: this morning I approved a PR by @benesjan that makes the event store substantially nicer
Bad news: this morning I approved a PR by @benesjan that makes the event store substantially nicer so I'll have to solve a bunch of conflicts :P

@benesjan benesjan removed their request for review January 13, 2026 17:58
@AztecBot AztecBot force-pushed the martin/staged-writes-in-tagging-stores branch from e3c729d to 9619e78 Compare January 14, 2026 09:05
Base automatically changed from martin/staged-writes-in-tagging-stores to next January 14, 2026 09:39
@mverzilli mverzilli added ci-squash-and-merge and removed ci-no-fail-fast Sets NO_FAIL_FAST in the CI so the run is not aborted on the first failure labels Jan 14, 2026
@mverzilli mverzilli enabled auto-merge January 14, 2026 11:33
@AztecBot
Copy link
Collaborator

AztecBot commented Jan 14, 2026

Flakey Tests

🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (8;;http://ci.aztec-labs.com/85940d1ef6a778f4�85940d1ef6a778f48;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_epochs/epochs_invalidate_block.parallel.test.ts "proposer invalidates multiple blocks" (604s) (code: 124) group:e2e-p2p-epoch-flakes (\033mverzilli\033: update comment)

@AztecBot AztecBot force-pushed the martin/staged-writes-in-private-events branch from 17914e7 to ee88b93 Compare January 14, 2026 12:20
@AztecBot AztecBot force-pushed the martin/staged-writes-in-private-events branch from ee88b93 to 08fb4a0 Compare January 14, 2026 12:23
@mverzilli mverzilli added this pull request to the merge queue Jan 14, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 14, 2026
@mverzilli mverzilli added this pull request to the merge queue Jan 14, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 14, 2026
@mverzilli mverzilli enabled auto-merge January 15, 2026 10:03
@AztecBot AztecBot force-pushed the martin/staged-writes-in-private-events branch from a874c13 to 8dddf6e Compare January 15, 2026 10:11
@AztecBot AztecBot force-pushed the martin/staged-writes-in-private-events branch from 8dddf6e to 96dfd77 Compare January 15, 2026 10:14
@mverzilli mverzilli added this pull request to the merge queue Jan 15, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 15, 2026
mverzilli and others added 2 commits January 15, 2026 16:22
Fourth part of the series started with #19445.

This makes the PrivateEventStore work based on staged writes. With this, private events aren't written to persistent storage until PXE decides to commit the job.
@mverzilli mverzilli force-pushed the martin/staged-writes-in-private-events branch from e6f491b to ef81e22 Compare January 15, 2026 16:25
@mverzilli mverzilli added the ci-no-fail-fast Sets NO_FAIL_FAST in the CI so the run is not aborted on the first failure label Jan 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-no-fail-fast Sets NO_FAIL_FAST in the CI so the run is not aborted on the first failure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants