This repository was archived by the owner on Apr 29, 2026. It is now read-only.
Chore/roundtrip property and threadsafety note#10
Merged
Conversation
added 2 commits
April 22, 2026 19:19
Hypothesis-driven tests covering the top-level contract users rely on: deanonymize(anonymize(x).text) == x. Two strategies — arbitrary safe text, and randomly-interleaved valid PII samples — extend hypothesis coverage past the validator layer to the full anonymize/deanonymize pipeline.
Spell out that Mapping (and therefore Shield) is not thread-safe: token_for mutates dicts and a counter without locking. Adds a paragraph to the Mapping docstring and a new 'Concurrency and thread safety' section to docs/limitations.md describing the one-Shield-per-thread and external-lock workarounds.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
No description provided.