cms-dev / cms-dev/cms

Ranking server sometimes loses some subchanges

Open
#1,261 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug rws
Dominant language
Python
Stars
1k
Forks
412
Avg merge
6d 10h
Merged PRs (30d)
3

Description

Description:

During IOI 2024 contest, we had a live stream, using scoreboard as a source of data for inforgrafics.
In particular, we are using /subchanges endpoint to receiver score updates. While not being optimal, for simplicity,
we just reload the whole endpoint every 5 seconds.

The problem is on the second day by some reason some of day1 submissions sumtimes disappeared from /subchanges endpoint and appeared back.

As an estimation here is log of 4-digit submission ids available requested several times.

/tmp/d1/message$ curl https://ranking.ioi2024.eg/subchanges/ | grep -oe '"submission": "...."' | wc -l
5383
/tmp/d1/message$ curl https://ranking.ioi2024.eg/subchanges/ | grep -oe '"submission": "...."' | wc -l
5383
/tmp/d1/message$ curl https://ranking.ioi2024.eg/subchanges/ | grep -oe '"submission": "...."' | wc -l
5373
/tmp/d1/message$ curl https://ranking.ioi2024.eg/subchanges/ | grep -oe '"submission": "...."' | wc -l
5373
/tmp/d1/message$ curl https://ranking.ioi2024.eg/subchanges/ | grep -oe '"submission": "...."' | wc -l
5383

There is normally 5383 submissions with 4-digit id, while 10 of them disappeared for some time, and then appeared back.

I'm not sure if it is cms bug, or setup problem, as I don't have any access to setup.

Expected: All submissions of the first day are always available during the second

Actual: They eventually disappears and appears back

Logs
System Information

Unfortunately, I don't have access to setup, so I have no logs.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing repeated requests to the /subchanges endpoint while contest data from the first day is present. Inspect the ranking server's endpoint handling and available setup logs; the issue provides no file or test references. Done means repeated requests consistently include all first-day submissions during the second day.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.