Date reported: 2026-03-28 Branch: feat/tournament Status: Open
In a tournament of 8 players, a player (bot1) failed to join their assigned match — likely due to a connection error. As a result, that match remained permanently "in progress" and the tournament was unable to complete.
- Create a tournament with 8 players.
- Simulate or trigger a connection failure for one of the players (e.g.,
bot1) before they join their assigned match. - Observe that the match is stuck in "in progress" state.
- The tournament cannot advance to the next round or reach a final result.
If a player fails to connect/join within a reasonable timeout, the tournament should either:
- Mark the absent player as a forfeit and advance their opponent, or
- Retry the connection and surface an error to the tournament host.
The tournament should always be able to reach a terminal state.
The match stays in "in progress" indefinitely. The tournament is blocked and cannot finish.
Unknown — possibly a connection drop, socket timeout, or missing error handling when a player fails to join a match room in the tournament flow. Needs investigation in the tournament match-joining logic and Socket.IO event handlers.
src/lib/server/socket/handlers/game.ts— match state sync- Tournament-related route/component handling match join events
- Observed during E2E testing (
test-results/tournament-Tournament-E2E--22479-join-and-start-a-tournament-chromium/) - Root cause not yet confirmed; further logging and debugging required