Skip to content

bug: auto-restore rounds after a server restart - #185

Open
lukepolo wants to merge 1 commit into
mainfrom
bug/round-restore-recovery
Open

lukepolo wants to merge 1 commit into
mainfrom
bug/round-restore-recovery

Conversation

@lukepolo

@lukepolo lukepolo commented Sep 19, 2026

Copy link
Copy Markdown
Contributor

A restarted server came back at 0-0, could be resumed, and published its own round 1 over the real one. Restoring that backup gave 6v4 and the score on the wrong side.

  • a server behind the backend holds the match (no resume, no round publishing) and restores the latest usable round by itself once everyone is back
  • restores requested short-handed are queued, not dropped; .resume during a recovery votes to restore now
  • backups are validated before upload and restore, restores are verified, and teams are re-enforced afterwards

Pairs with 5stackgg/api#419, which stops a recorded round from being overwritten.

- a server that is behind the backend (restart, map reload) can no longer be
  resumed or publish rounds; it holds the match and restores the latest usable
  round on its own once the roster is whole
- a restore requested while short-handed is queued instead of dropped, and
  .resume during a recovery votes to restore with whoever is here
- backups are validated before upload and before restore: right round, and
  players in both PlayersOnTeam sections
- a restore is verified, teams are re-enforced after it, and the in-memory
  round list no longer keeps stale duplicates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant