Conversation
- a score for a round that is already recorded (or an earlier one) comes from a server that is behind the backend; it is rejected and the server is told to re-sync instead of overwriting the real round and its backup - an identical redelivery is a no-op, and may only fill in a missing backup - a backup with no players or for another round is stored as no backup - rounds replayed after a restore are unaffected: the restore soft-deleted the ones they replace
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
1 participant
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.
A restarted game server came back at 0-0 and published its own round 1. The score upsert overwrote the real round and its backup file, so the later restore loaded a backup with no players in it.
get_matchto re-syncPairs with 5stackgg/game-server#185.