fix: add max prunes to pruner#4191
fix: add max prunes to pruner#4191MasterPtato wants to merge 1 commit into02-12-fix_add_max_param_to_prune_signals_cmdfrom
Conversation
|
🚅 Deployed to the rivet-pr-4191 environment in rivet-frontend
|
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
PR Review: fix: add max prunes to prunerOverall: Small, well-targeted fix. The logic is correct and addresses a real risk of unbounded transaction sizes in the pruner. What the change doesThe pruner loops over FDB key ranges inside transactions and deletes workflow data. Before this fix, a single transaction could process an unlimited number of entries, bounded only by the 3-second CorrectnessThe pagination logic is sound. When the inner loop breaks due to hitting the limit, One pre-existing nuance: the Observations
Timeout interaction (pre-existing): When Magic number: The value 1000 is reasonable but has no comment explaining the rationale (e.g. staying well within FDB's 10 MB transaction write limit). A brief inline comment would help future readers. Summary
The core fix is solid. The observations above are all pre-existing issues or minor nits that do not block the change. |
6d76467 to
d19b48a
Compare
832c05a to
6804587
Compare
d19b48a to
9f9271d
Compare
6804587 to
9561940
Compare
9f9271d to
dbb33f8
Compare
9561940 to
1ae21ab
Compare
1ae21ab to
c37f972
Compare
c37f972 to
603d888
Compare
dbb33f8 to
8f1ddf6
Compare
603d888 to
1e27716
Compare
Merge activity
|
# Description Please include a summary of the changes and the related issue. Please also include relevant motivation and context. ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update ## How Has This Been Tested? Please describe the tests that you ran to verify your changes. ## Checklist: - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context.
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Checklist: