Contest scoreboard clock is running at local time
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
The _get_time() function in cms/cmsranking/static/TimeView.js makes use of the local time. This means that, if one runs a contest in which there is a delay in between the server time and the local time, the scoreboard clock starts with negative values.
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 in cmsranking/static/TimeView.js at the _get_time() function and inspect how the scoreboard clock obtains its time. Reproduce the clock with a server/local time offset, then verify that the contest clock no longer begins with negative values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100