Scoring appears to have stalled since Oct 23 19:50-20:37 KST (about 2 days) in Seasons 2, 3 and 4 (submissions accepted, no scores returned)
Hello,
We are reporting what looks like a backend issue, in case it is not yet known.
Observed from three public leaderboards as of Oct 25 23:40 KST:
Season 2 (7,077 rows): most recent scored_at is Oct 23 20:37. Zero entries scored
on Oct 24 or Oct 25, across all teams. Daily scored counts: Oct 21 = 34, Oct 22 = 119, Oct 23 = 5, Oct 24 = 0, Oct 25 = 0.
Season 3 (5,316 rows): most recent scored_at is Oct 23 20:08. Zero entries scored
on Oct 24 or Oct 25. Daily scored counts: Oct 21 = 42, Oct 22 = 83, Oct 23 = 64, Oct 24 = 0, Oct 25 = 0.
Season 4 (4,270 rows): most recent scored_at is Oct 23 19:50. Zero entries scored
on Oct 24 or Oct 25. Daily scored counts: Oct 21 = 85, Oct 22 = 77, Oct 23 = 51, Oct 24 = 0, Oct 25 = 0.
Eight submissions we made on Oct 23 at 21:06 were accepted (HTTP 200) and have no score.
On Oct 26 at 16:13-16:17 we submitted 30 more; all were accepted and none is scored yet.
All three seasons stop within about 45 minutes of each other and none has scored anything
in the roughly two days since, so this does not look season-specific.
- The submission endpoint returned HTTP 503 from roughly Oct 24 00:34 to 15:09 KST
(~14.5 hours), then recovered. Submissions are accepted normally since then. - The acceptance responses return
queue_positionvalues that keep growing (57 through 86
earlier; 118 through 147 for our Season 4 submissions on Oct 26). That is a direct signal
from your own API that a backlog has built up and is not draining.
This suggests the submission API and the scoring worker recovered separately, and the
scoring worker may still be down.
Two questions:
- Is the scoring backlog expected to clear on its own, or does the worker need a restart?
- Submissions accepted during this window still consume a daily slot. Will they be scored
once the worker resumes, or should we treat them as lost?
We are not asking for quota compensation and we are not disputing any score. We only need to
know whether submissions made now will eventually return results, so we can decide whether to
keep spending daily slots blind.
Thank you,
1Dmeds
μ±μ μ λ©μΆμ§ μμμ΅λλ€. λ©μΆ κ²μ μμνμ λλ€. κ·Έλ¦¬κ³ λ³΄λ΄μ£Όμ μ¦κ±° νλκ° λ°λ‘ κ·Έ κ³ μ₯μ μ¦μμ λλ€.
λ³΄κ³ κ° μ λ°νμ΅λλ€. νΉν queue_position μ΄ κ³μ 컀μ§λ€λ κ΄μ°°μ΄ μμΈμ νΉμ νλ λ° κ²°μ μ μ΄μμ΅λλ€.
μ€μΈ‘ (2026-10-26 16:48 UTC)
| μμ¦ | μ μΆ | κ²°κ³Ό κΈ°λ‘λ¨ | μ€μ λ―Έμ±μ | μμνμ μ¬λΌμ¨ μ |
|---|---|---|---|---|
| μμ¦2 | 7,219 | 7,219 | 0 | 7,058 |
| μμ¦3 | 5,359 | 5,359 | 0 | 5,308 |
| μμ¦4 | 4,444 | 4,428 | 16 (μ²λ¦¬ μ€) | 4,267 |
λ§μ§λ§ μ±μ μ 10μ 26μΌ 16:35 UTC μ λλ€. 24μΌκ³Ό 25μΌμλ μ±μ μ΄ λμμ΅λλ€. μμνμ μ¬λΌμ¨ μμ κ²°κ³Ό κΈ°λ‘ μμ μ°¨μ΄κ° μ§κΈ 보μ΄μ§ μλ λΆλμ λλ€.
queue_position μ λνμ¬
/api/queue μ scored λ κ²°κ³Ό νμΌ μκ° μλλΌ μμν νλͺ© μμμ μ΅λλ€. queued = total - scored λ‘ κ³μ°ν©λλ€. μμνκ° 10μ 23μΌμ λ©μΆλ©΄μ scored κ° κ³ μ λκ³ , μ μΆμ΄ λ€μ΄μ¬μλ‘ queued λ§ μ»€μ‘μ΅λλ€. μ§κΈ κ°μ 161, 51, 177 μ
λλ€. μ ν¬ API κ° μ μ²΄κ° μμ΄λ κ²μ²λΌ 보μ΄λ μ νΈλ₯Ό 보λκ³ , κ·Έ ν΄μμ ν©λΉνμ΅λλ€. μ€μ μ 체λ 0, 0, 16 μ
λλ€.
μμΈ
μμν νμΌμ΄ 10MBλ₯Ό λμ μ μ₯μκ° κ·Έ νμΌμ λμ©λ μΆμ μΌλ‘ μλ μ ννμ΅λλ€. λμ©λ νμΌ μ°κΈ°κ° μ‘°μ§ μ μ₯μ©λ νλμ κ±Έλ € κ±°μ λκ³ μμ΅λλ€. μμ κ²°κ³Ό νμΌμ μν₯μ λ°μ§ μμ μ μμΌλ‘ μ¨μ§λλ€. κ·Έλμ μ±μ μ λκ³ κ³΅κ°λ©΄λ§ λ©μΆ° μμ΅λλ€. μ ν κ·μΉμ΄ κ²½λ‘κ° μλλΌ νμΌ μ΄λ¦μΌλ‘ λ§μ μΈ μμ¦μ΄ κ°μ λ ν¨κ» λ§νμ΅λλ€.
μ§λ¬Έμ λν λ΅
- μ μ²΄κ° μ€μ€λ‘ ν리λμ§, μ컀 μ¬μμμ΄ νμνμ§: μ¬μμμ νμ μμ΅λλ€. μ컀 7κ°κ° λκ³ μμ΅λλ€. 16:44 UTC μ 18건μ΄λ λ―Έμ±μ μ΄ 16:48 μ 16건μΌλ‘ μ€μμ΅λλ€. νμ΄μΌ ν μ 체 μμ²΄κ° μμ΅λλ€. λ³΅κ΅¬κ° νμν κ²μ μμνμ λλ€.
- μ΄ κΈ°κ° μ μΆμ΄ μ±μ λλμ§, λ²λ €μ§ κ²μΌλ‘ λ΄μΌ νλμ§: μ΄λ―Έ μ±μ λμ΅λλ€. 10μ 23μΌ 21μ μ μΆλΆ 8건과 10μ 26μΌ μ μΆλΆ 30건μ νμΈνκ³ , 1Dmeds λ κ³μ μ λ―Έμ±μ μ 0건μ λλ€. μ§κΈ λ¨μ λ―Έμ±μ 16건μ 10μ 26μΌ 15μ 30λΆλμ λ€μ΄μ¨ λ€λ₯Έ ν λ¬Άμμ΄κ³ μμλλ‘ μ²λ¦¬λκ³ μμ΅λλ€. λ²λ €μ§ κ²μ μμ΅λλ€.
κ·Έλ¬λ ν루 λͺ«μ μ°λ©΄μ λμ κ°λ¦¬κ³ μ μΆνλ μν©μ μλλλ€. κ²°κ³Όλ λ¨μ μκ³ , 보μ΄μ§ μλ κ²λΏμ λλ€.
503 ꡬκ°(10μ 24μΌ 00:34μμ 15:09 KST)μ λ³κ°λ‘ νμ΄μ§ μͺ½ λ¬Έμ μκ³ λ³΅κ΅¬λμ΅λλ€. μ μΆ κ²½λ‘μ μ±μ κ²½λ‘κ° λ°λ‘ 볡ꡬλλ€λ μ§μ μ΄ λ§μ΅λλ€.
λ€μ
μμν 볡ꡬ본μ μΈ μμ¦ λͺ¨λ λ§λ€μ΄ κ²μ¦μ λ§μ³€μ΅λλ€. μ΄λ―Έ μ¬λΌμ μλ νλͺ©μ κΈμ λ¨μλ‘ μ¬νν μ μλμ§ λ¨Όμ νμΈνκ³ , νλλΌλ μ¬λΌμ§κ±°λ κ°μ΄ λ¬λΌμ§λ©΄ μ¬λ¦¬μ§ μλλ‘ ν΄ λμμ΅λλ€. μ μ₯μ©λ κ±΄μ΄ ν΄μ λλ©΄ λ°λ‘ μ μ©νκ³ μ΄ κΈμ μ κ² μ΅λλ€.
μμνκ° κ²°κ³Όλ₯Ό λ°λΌμ€κ³ μλμ§ λ³΄λ μ κ²λ κ°μμ λ£κ² μ΅λλ€. μ΄λ² κ³ μ₯μ μ ν¬ κ°μλ‘λ 보μ΄μ§ μμκ³ , λ λ² λͺ¨λ μ°Έκ°μκ° λ¨Όμ μλ € μ£Όμ ¨μ΅λλ€.
Scoring never stopped. The leaderboard did. One piece of your own evidence is a symptom of that failure.
Your report was precise, and the observation that queue_position keeps growing is what pinned down the cause.
Measured at 2026-10-26 16:48 UTC
Season 2: 7,219 submitted, 7,219 results written, 0 unscored, 7,058 on the leaderboard.
Season 3: 5,359 submitted, 5,359 results written, 0 unscored, 5,308 on the leaderboard.
Season 4: 4,444 submitted, 4,428 results written, 16 in progress, 4,267 on the leaderboard.
The most recent score was written on 26 October at 16:35 UTC. Scoring also ran on the 24th and the 25th. The gap between results written and rows on the leaderboard is what is currently invisible.
About queue_position
In /api/queue, scored is taken from the number of leaderboard rows, not the number of result files, and queued is total - scored. When the leaderboard froze on 23 October, scored froze with it, so queued grew with every new submission. It currently reads 161, 51 and 177. Our own API produced a signal that looked like a growing backlog, and reading it that way was reasonable. The real backlog is 0, 0 and 16.
Cause
Once the rollup file passed 10MB, the repository moved it to large file tracking, and large file writes are being refused against an organization storage limit. Small result files are unaffected and keep writing, so scoring runs while the public view stays frozen. The tracking rule matches by file name rather than path, so all three seasons were blocked on the same day.
Your questions
- No restart is needed. Seven workers are running, and unscored submissions went from 18 at 16:44 UTC to 16 at 16:48. There is no backlog to drain. What needs recovery is the rollup.
- They are already scored. We checked the eight submissions from 23 October and the thirty from 26 October, and your account has zero unscored entries. The 16 that remain belong to a separate batch submitted around 15:30 UTC on 26 October and are being worked through in order. Nothing is lost.
So you are not spending daily slots blind. The results exist, they are just not visible yet.
The 503 window on 24 October was a separate problem on the page side and has recovered. Your inference that the submission path and the scoring path recovered separately is correct.
Next
Restored rollups are built and verified for all three seasons. We first confirmed that existing rows reproduce character for character, and the upload refuses to proceed if any existing row would disappear or change. It will be applied as soon as the storage item is cleared, and we will post here when it is.
We will also add a check that the rollup is keeping up with the results. Our monitoring could not see this failure, and on both occasions a participant found it first.
μ μ©λμ΅λλ€. μμνκ° λ³΅κ΅¬λμ΅λλ€.
| μμ¦ | μ¬λΌμ€μ§ λͺ»νλ μ±μ | 볡ꡬ ν μμν | μ°Έκ°μ νλ©΄ λκΈ° |
|---|---|---|---|
| μμ¦2 | 161 | 7,219 | 0 |
| μμ¦3 | 51 | 5,359 | 0 |
| μμ¦4 | 177 | 4,444 | 0 |
λ§μνμ queue_position λ μΈ μμ¦ λͺ¨λ 0μΌλ‘ λ΄λ €κ°μ΅λλ€. κ·Έ κ°μ΄ 컀μ§λ κ²μ μ μ²΄κ° μλλΌ μμνκ° λ©μΆ κ²°κ³Όμκ³ , μ§μ ν΄ μ£Όμ λλΆμ κ·Έ μ§μ μ μ°Ύμμ΅λλ€.
μμνλ₯Ό 10MB μλ μ‘°κ°μΌλ‘ λλ μ°λ λ°©μμΌλ‘ λ°κΏ¨κ³ , μ±μ κΈ°λ κ°μ λ°©μμΌλ‘ κ΅μ²΄νμ΅λλ€. μ¬λ¦° λ€ λμ½μ΄ μλ³Έκ³Ό κΈμ λ¨μλ‘ κ°μμ§ νμΈνμ΅λλ€.
μ μλ μ΄λ―Έ κ³μ°λΌ μλ κ°μ΄λΌ λ°λμ§ μμμ΅λλ€. μ¬μ μΆμ νμ μμ΅λλ€.
Applied. The leaderboard is restored.
Season 2: 161 entries now visible, 7,219 total. Season 3: 51, now 5,359. Season 4: 177, now 4,444. queued is now 0 for all three.
The growing queue_position you reported was not a backlog, it was the frozen rollup showing through, and your report is what located it.
The rollup is now written as text shards under the size limit, and the scorer was switched to the same format. We read the uploaded result back and confirmed it matches the source character for character. The scores themselves were already computed and are unchanged, so no resubmission is needed.
λ§κ° μ‘°μ κ²°κ³Όμ λλ€. μμ¦2 λ§κ°μ 10μ 31μΌ κ·Έλλ‘μ΄κ³ , μ°μ₯νμ§ μμ΅λλ€.
보μμ μꡬνμ§ μμΌμ λ€κ³ λ¨Όμ λ°ν μ£Όμ ¨μ§λ§, μμ λ³λ 곡μ§λ₯Ό μ½μνμΌλ―λ‘ κ²°κ³Όλ₯Ό μ ν©λλ€.
νλ¨ κ·Όκ±°λ μ μκ° μ¬λΌμ§ μ μ΄ μκ³ μ§κΈμ μ λΆ λ³΄μΈλ€λ μ μ
λλ€. νμ¬ μ μμ¦ λ―Έμ±μ 0, queued 0μ
λλ€.
λ¨μ κΈ°κ°μ μν΄ μμ¦2 μ±μ λ₯λ ₯μ λ λ°°λ‘ μ¬λ Έκ³ , μμνκ° κ²°κ³Όλ₯Ό λ°λΌμ€λμ§ λ³΄λ μ κ²μ κ°μμ λ£μμ΅λλ€. μ§μ νμ γλ§κ° μ§μ μ λκΈ°μ΄μ΄ κΈΈμ΄μ Έ κ°μ μΌμ΄ λ°λ³΅λ μμ§γκ° λ°λ‘ κ·Έ μ‘°μΉμ μ΄μ μ λλ€. λ€λ§ μ°Έκ°μ μ μμ΄ λ§μ§λ§ λ μ νλλ₯Ό λ€ μ°λ©΄ κ·Έλλ λ°λ¦½λλ€.
μ 체 곡μ§λ λ³λλ‘ μ¬λ Έμ΅λλ€.
The deadline decision: Season 2 closes on 31 October as scheduled, and will not be extended.
You said up front that you were not asking for quota compensation, but we promised a separate announcement, so here is the outcome.
The reasoning is that no score was lost and everything is visible now. Unscored submissions are at zero across all seasons and queued reads zero.
For the remaining days, Season 2 scoring capacity is doubled and monitoring now checks whether the rollup is keeping up with the results. Your point about the queue growing near a deadline is exactly why. If every entrant uses a full daily quota on the last day there will still be a wait.
A separate announcement covers this for all participants.
κ²°μ μ΄ λ°λμμ΅λλ€. μμ¦2 λ§κ°μ 11μ 7μΌλ‘ 1μ£Ό μ°μ₯ν©λλ€.
κ°μ λ μμ γμ°μ₯νμ§ μμ΅λλ€γλΌκ³ μ μμ΅λλ€. κ·Έ λ€ λ¨μ κΈ°κ°μ μ²λ¦¬ λ₯λ ₯μ μ€μΈ‘νκ³ , κ²°κ³Όμ λ°λΌ λ°κΏ¨μ΅λλ€.
λ¨μ 4μΌμ λ€μ΄μ¬ μ μλ μ΅λ μ μΆλμ΄ 720건(νλ κ³μ 6κ³³ Γ ν루 30건)μΈλ° λΉμ λ₯λ ₯μ 560건μ΄μμ΅λλ€. λ₯λ ₯μ λ λ°°λ‘ μ¬λ Έμ§λ§ μ‘°μ©νλ κ³μ μ΄ λ§κ° μ μ λμμ€λ©΄ μ¬μ κ° μμ 건μΌλ‘ μ€μ΄λλλ€. μ§μ νμ γλ§κ° μ§μ μ λκΈ°μ΄μ΄ κΈΈμ΄μ Έ κ°μ μΌμ΄ λ°λ³΅λ μμ§γκ° λ°λ‘ κ·Έ κ³μ°μμ νμΈλμ΅λλ€.
보μμ μꡬνμ§ μμΌμ λ€κ³ λ¨Όμ λ°ν μ£Όμ ¨μ§λ§, κ²°μ μ΄ λ°λμμΌλ μ ν΄ λ립λλ€. μ λ§κ°μ 11μ 7μΌμ΄κ³ μ μ νμ΄μ§μ 보λ νκΈ°λ λ°κΏ¨μ΅λλ€. μ 체 곡μ§λ #11 μ μμ ν΄ μ¬λ Έμ΅λλ€.
The decision has changed. Season 2 is extended by one week, to 7 November.
Earlier the same day we wrote that the deadline would not be extended. We then measured the scoring capacity available for the remaining days and changed the decision.
Up to 720 submissions could arrive in four days (6 recently active accounts at 30 per day) against a capacity of about 560. We doubled capacity, but if quiet accounts return before the deadline the margin falls to a few dozen entries. Your point about the queue growing near a deadline is exactly what that calculation confirmed.
You said up front that you were not asking for compensation, but the decision has changed so we are telling you. The new deadline is 7 November, and the submission page and board now show it. The full notice is revised in #11.