submit: poll for verdict on AtCoder and Codeforces #302

New issue

Closed

opened 2026-03-05 06:35:22 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-03-05 06:35:22 +00:00

After `:CP submit`, AtCoder and Codeforces return `verdict='submitted'` immediately. The actual result (AC/WA/TLE/MLE/RE) is never surfaced to the user.

Both scrapers should poll for the verdict after the form is submitted and emit `{"status": "..."}` ndjson events as updates arrive, with the final verdict displayed in the Lua notification. CSES already does this correctly via its polling endpoint.

AtCoder: poll the submission URL or `/submissions/me` for the verdict row
Codeforces: poll `/contest/{id}/my` or the `contest.status` API endpoint

The 120s ndjson timeout in `scraper.lua` already accommodates long-running submit processes.

After \`:CP submit\`, AtCoder and Codeforces return \`verdict='submitted'\` immediately. The actual result (AC/WA/TLE/MLE/RE) is never surfaced to the user. Both scrapers should poll for the verdict after the form is submitted and emit \`{"status": "..."}\` ndjson events as updates arrive, with the final verdict displayed in the Lua notification. CSES already does this correctly via its polling endpoint. - AtCoder: poll the submission URL or \`/submissions/me\` for the verdict row - Codeforces: poll \`/contest/{id}/my\` or the \`contest.status\` API endpoint The 120s ndjson timeout in \`scraper.lua\` already accommodates long-running submit processes.