Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make an easy-to-search "tournament actions log" #1433

Open
domino14 opened this issue Feb 11, 2025 · 0 comments
Open

make an easy-to-search "tournament actions log" #1433

domino14 opened this issue Feb 11, 2025 · 0 comments

Comments

@domino14
Copy link
Collaborator

domino14 commented Feb 11, 2025

From time to time tournament bugs get reported. For example:

In the /tournament/(snip) I ran Div A and B last week. When I start a new round on Round 4. The pairing for Div B was done suddenly but when I run Div A, Woogles said there are no settings for Div A. However, when I did the round control settings, I completed Div A and then copied from Div A to Div B.
This was strange and I corrected it by manually pairing the whole Div A. After that, Round 5 worked well for both Div A and B.

This is very hard to debug after the fact, and many tournaments have been run without seeing these kind of bugs.

It would be nice to have a way to replicate the state of a tournament from a log of tournament actions, starting from creating the tournament all the way to individual game submissions (either by the players or the director). Basically any action involving the tournament. Then we can try replaying and regenerating state from these if possible. Even showing actions like this to directors could be useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant