Revert buggy workaround for race conditions in chat store #3726
Conversation
This file contains 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.
This "workaround" solved the race conditions (#3716) but didn't prevent other buggy behaviour around the chat store, and even worse, these issues affect the user now: When switching accounts after deleting a chat, the message list is blank, similar issues can come up when using the 2nd device flow.
For now we roll back that change, getting back to these race conditions and occasional exceptions, which at least do not affect the user. This is a temporary solution.
For a real fix we're looking into a chat store logic refactoring which will take a little bit more time, pending PR here: #3725