Repository navigation
fix(dataset): invalidate fetched records after deletion #918
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
Open
Gareth.Y (linjiaye929)
wants to merge
2
commits into
braintrustdata:main
Choose a base branch
from
linjiaye929:codex/fix-dataset-delete-cache
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 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.
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.
When callers bulk-delete by invoking
delete()while iterating this sameDataset, this resets_fetched_dataeven thoughObjectIterator.__next__()retains its numeric index and calls_refetch()for every next item. Every deletion therefore forces another full, paginated download (making an n-row cleanup O(n²)); once a deletion is visible afterflush()or a background publish, the shorter list is indexed with the old offset and rows are skipped, so the loop can leave records undeleted. Cache invalidation needs to preserve the snapshot used by an active iterator or otherwise account for its position.Useful? React with 👍 / 👎.
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.
Thanks, this reproduces. With four records, deleting and flushing each row during iteration visited only IDs
0and2, leaving1and3behind. The advancing iterator index was being applied to a newly fetched, shorter list.The follow-up makes each iterator retain the sequence from its first successful fetch. Existing iterators keep a stable snapshot, while new iterators see the invalidated/refreshed dataset cache. The deletion loop now visits all four records with one fetch for that active iterator.
Regression coverage includes delete-and-flush during iteration, fresh iterators, stable empty/exhausted iterators, failed initial fetch retries, and the shared Experiment pagination path. The focused offline set passes 20 tests, and an independent review also reproduced the issue and reran that set. Tests isolate local behavior using mocked backend responses; live service behavior and full CI have not been validated.
Implemented in
98ea56114999d9204f56cc326b03cfc599a6107d.