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.
Changes
Notes
Unfortunately this was being caused by broadcasting the lock/unlock of a storyline to all clients. I believe we had this as a benefit that all clients would be able to know when a storyline was locked/unlocked. However, in certain situations, a client would take the secret key of another client instead of the one they requested. Consider the following example:
We can see here that the result is dependent on the order of operations, and when you have multiple clients, as was the case in the testing party, chaos ensues!
The easiest fix was for the wss to respond only to client requesting the storyline lock/unlock and change a few order of operations. Unfortunately this does mean we lose out on the benefit stated above, but it does remove the possibility of any race conditions. In case we want to add it back, I have opted to comment it out instead of removing it altogether.
Testing
Steps:
This change is