This repository has been archived by the owner on Dec 30, 2022. It is now read-only.
Fix the majority of verification race conditions #5
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
Data races can probably still occur in the following cases: - If Discord is still adding the role when we fetch the user for the second time - If we don't all verify, for example if someone does a kick and someone else does a verify These are substantially less likely than the common case, which has happened several times now
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
There is currently a high potential for race conditions when multiple verifiers attempt to verify a user at the same time. This PR fixes the majority of these cases
Data races can probably still occur in the following cases:
These are substantially less likely than the common case, which has happened several times now