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

Thread safety of using Anonymize/Deanonymize #131

Open
StefanKarlsson321 opened this issue May 3, 2024 · 0 comments
Open

Thread safety of using Anonymize/Deanonymize #131

StefanKarlsson321 opened this issue May 3, 2024 · 0 comments

Comments

@StefanKarlsson321
Copy link

Hi!

I have looked into the Deanonymize and Anonymize scanners and they seem inherently unsafe to call concurrently since the usage of Vault is unsafe (unprotected non-atomic read-write). Am I correct? I am wondering if the aim is to support concurrent calls or not in general, and in which way? It would be nice it if there was proper documentation on how to best use scaners in a multi-threaded environment.

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

No branches or pull requests

1 participant