Introduce RWS freezing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
Currently, in order to freeze the ranking, one can just kill ProxyService so that no more data will be sent to RWS. However, it would be useful to just inform RWS of the freezing, so that it will stop showing the new data to the spectator (even though data is being received).
This is useful, for example, when the ranking is meant to be "unfrozen" several hours after the end of the contest (when the servers will already be shut down as well as ProxyService).
P.S. this is not related to unfreezing animations (as in ACM ICPC) and such, even though that would be cool
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how ProxyService sends ranking data to RWS and identify the existing control path used when ProxyService is stopped. Define the RWS notification needed to freeze spectator updates while data continues arriving, and verify that ranking can later be unfrozen after the contest servers and ProxyService are shut down.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100