fix: prune old proposer preferences submissions#9591
Conversation
There was a problem hiding this comment.
Code Review
This pull request introduces a mechanism to prune past epochs from the submitted tracking map in ProposerPreferencesService, preventing unbounded memory growth. It also adds a corresponding unit test to verify that past epochs are correctly deleted while the current epoch is retained. There are no review comments, so no further feedback is provided.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
d48f2b3 to
7583a02
Compare
7583a02 to
0fb52bb
Compare
nflaig
left a comment
There was a problem hiding this comment.
LGTM, self-review since this was implemented by claude
Performance Report✔️ no performance regression detected Full benchmark results
|
Motivation
Follow-up to #9571. The
submittedmap inProposerPreferencesServicetracks which preferences were sent per epoch but was never pruned, so it grows by one entry each epoch for the lifetime of the process. Raised in review by @twoeths.Description
Drop tracking for past epochs at the start of each task run; only
currentEpochandcurrentEpoch + 1are ever processed.