8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
4f8765b
a7b78d8
c5f138c
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Does this create a copy of the passed user_attributes, so it's not reflected when the client copy is changed later?
Sorry, something went wrong.
"set_attribute" can be called concurrently with get-attributes from the userContext. Don't we need to synchronization for attributes read/write?
Can we add a test - when the caller change its attribute copy after userContext is created, it should not be reflected to userContext?