chore: make AccountManager concurrency safe - WPB-23570#4340
Open
samwyndham wants to merge 5 commits intodevelopfrom
Open
chore: make AccountManager concurrency safe - WPB-23570#4340samwyndham wants to merge 5 commits intodevelopfrom
AccountManager concurrency safe - WPB-23570#4340samwyndham wants to merge 5 commits intodevelopfrom
Conversation
|
Contributor
Test Results 1 files 132 suites 21s ⏱️ For more details on these failures, see this check. Results for commit 0e4704b. Summary: workflow run #22222448426 |
|
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.



Issue
This PR makes
AccountManager,AccountStore&AccountSendableand therefore thread safe. It is part of a larger effort to make Session management safer across concurrent contexts.I intentionally chose to do this with the aid of locks instead of Actors or @mainactor annotation as:
awaitkeyword.The negative is there is some additional complexity added to these types themselves.
Note:
I tried to add some tests checking for threading issues but was unsuccessful. I could do it by enabling the thread sanitizer in the test plan and having tests fail on error but there were too many existing tests that would fail in such cases.
Testing
Checklist
[WPB-XXX].UI accessibility checklist
If your PR includes UI changes, please utilize this checklist: