-
-
Notifications
You must be signed in to change notification settings - Fork 67
fix(audit): prune expired events in bounded batches #605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
matteius
merged 3 commits into
opensensor:main
from
davlaw:fix/audit-prune-bounded-batches
Sep 13, 2026
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed — the budget is checked only after
sqlite3_step()returns, so it can't bound a single batch that is slow on I/O or waiting on a busy timeout. I've narrowed the guarantee rather than trying to enforce it inside the statement: the code comments already said the budget "bounds how many batches a pass runs, not the pass itself" and that "no maximum hold time is promised", and the PR description, which still claimed a bound "regardless of storage speed", now says explicitly that it is not a wall-clock bound on mutex hold time.What the change does guarantee is a row-count cap per statement (2,000 via the indexed
occurred_at, idordering) plus a between-statement budget, so work per pass is proportional to the batch size instead of the backlog. Interrupting a statement mid-flight via a progress handler would roll back that batch's work and needs its own retry/backoff design, so I've left it out of scope here.