Skip to content
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

Fix value table iteration vs log processing race #230

Merged
merged 4 commits into from
Oct 18, 2023
Merged

Conversation

arkpar
Copy link
Member

@arkpar arkpar commented Oct 16, 2023

Fixes #227

Copy link
Collaborator

@cheme cheme left a comment

Choose a reason for hiding this comment

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

change filled to written makes sense to me.
iiuc the _iteration_lock is needed for the linked issue where get_keys is doing iteration on key concurrently to db normal usage, and change in test is needed to reflect filled.
Maybe would be good to have such use case in testing or fuzzing (iter_while calls against standard usage of db), but not sure what would be appropriate here.

@arkpar arkpar merged commit 70e0929 into master Oct 18, 2023
9 checks passed
@arkpar arkpar deleted the arkpar/iter_fix branch October 18, 2023 08:20
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.

Panic on TableFile::slice_at.
2 participants