fix(memory): keep Bloom membership correct after insertion - #91
Open
mazzasaverio wants to merge 1 commit into
Open
mazzasaverio wants to merge 1 commit into
mazzasaverio wants to merge 1 commit into
Conversation
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A negative Bloom filter lookup remained cached after insertion, hiding newly added entries. Clear membership caches after add(), validate parameters and allocate at least one bit. Regression tests cover cached misses, Unicode, repeated additions, existing members and invalid sizing.
Validation: 11 focused tests passed. Full CI passed 528 tests per test-matrix job with 95.15% coverage, plus quality, docs, performance, property, packaging and installed-wheel checks. Local full-suite execution ended with exit 137 during ONNX, so CI supplies that evidence: https://github.com/ma2za/pseudonymize/actions/runs/36972349695 . No detector thresholds or dependencies change.