Skip to content

Conversation

@benesjan
Copy link
Contributor

@benesjan benesjan commented Jan 2, 2026

In this PR I move tagging related functionality around in order for it to be in a resonable place. Not done before to have the previous PRs be reviewable.

The sender sync algo was implemented first and for this reason it was in tagging/sync dir. In this PR I moved it to tagging/sender_sync and move a bunch of other stuff around.

// Having a large window significantly slowed down `e2e_l1_with_wall_time` test as there we perform sync for more than
// 1000 secrets. For this reason we set it to a relatively low value of 20. 20 should be sufficient for all the use
// cases.
export const UNFINALIZED_TAGGING_INDEXES_WINDOW_LEN = 20;
Copy link
Contributor Author

@benesjan benesjan Jan 2, 2026

Choose a reason for hiding this comment

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

This is shared between sender and recipient sync algos so made sense to move it index.ts in the parent dir.

@benesjan benesjan changed the base branch from 12-23-feat_expanding_return_value_of_getlogsbytags to graphite-base/19289 January 2, 2026 17:48
@benesjan benesjan force-pushed the graphite-base/19289 branch from f3df451 to c81bf33 Compare January 2, 2026 18:21
@benesjan benesjan force-pushed the 01-02-refactor_final_tagging_cleanup branch from ba9816c to d47f725 Compare January 2, 2026 18:21
@benesjan benesjan changed the base branch from graphite-base/19289 to 12-23-feat_expanding_return_value_of_getlogsbytags January 2, 2026 18:22
@benesjan benesjan force-pushed the 01-02-refactor_final_tagging_cleanup branch from d47f725 to 0be558e Compare January 2, 2026 18:23
@AztecBot AztecBot force-pushed the 12-23-feat_expanding_return_value_of_getlogsbytags branch 2 times, most recently from 6d58c3d to ceabd1c Compare January 2, 2026 18:46
Base automatically changed from 12-23-feat_expanding_return_value_of_getlogsbytags to next January 2, 2026 19:18
@benesjan benesjan force-pushed the 01-02-refactor_final_tagging_cleanup branch from 0be558e to 8e0f190 Compare January 2, 2026 19:20
@benesjan benesjan marked this pull request as ready for review January 2, 2026 19:21
@benesjan benesjan requested a review from mverzilli January 2, 2026 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants