Ability to terminate a tournament

[RoopjeetSingh]

Once we start it, even if we messed something up it just cannot stop. We need a way to stop it midway.

[KaustAbhinand]

Hi! I would like to take this issue, could you please mention which files to check and the expected results? Thanks!

[RoopjeetSingh]

Yes sure, the folder is called Tournament and it has everything about tournament. It is pretty separate from the other folders so you can easily make changes.

[KaustAbhinand]

I have already checked the repository, however there are other sub folders in Tournament, I wanted to know which ones in that are relevant for the bug.

[RoopjeetSingh]

So every folder has application, domain, and infra subfolders. Application is the folder that has the actual business layer/service logic. Domain is the folder with the tables and the DTOs, and Infra is the folder with the controller and Repository (these are all SpringBoot terms; if you don't know them, just ask GPT or Claude about it).
You will have to understand the table structures, etc.
As for the logic of how to terminate, that's all on you. You would have to understand the folder and how to terminate a tournament. One way could be setting all matches for the tournament to failed but even that may have syncronization issues. You could make any number of changes you want.
If you do make any changes to the tables, let @jaeheonshim know so that he can tell you the exact process of what to do when you change any tables.
Btw the test folder has a tournament folder with tests for the tournament. Please ensure that ./gradlew test works for you and yeah that's about it
Please let me know if you have any more questions

[KaustAbhinand]

Alright then! I'll submit a PR soon, please provide the output expected.
Thanks!

[RoopjeetSingh]

Expected output: an admin API in the admin controller that terminates the tournament such that no new games or matches (every match has 5 or 7 games) in the tournament are scheduled and all previously played and scheduled games and matches are set as failed. There are no latency requirements and hence it can take time but it should only send a response after it is done with the entire process even if it takes sometime (it shouldn’t schedule an asynchronous task and just return an output early). The output of the api is just 204 No content but success.
Don’t delete the tournament from the database though, nothing in the tables should be deleted with this api