From 855228c9a78efda598b6b3cad5914ec23951baaa Mon Sep 17 00:00:00 2001 From: Jaap Eldering Date: Mon, 15 Dec 2025 23:29:43 +0100 Subject: [PATCH] Runs should (must at WFs) get published as soon as available Closes: #222 --- Contest_API.md | 3 +++ Contest_Control_System_Requirements.md | 5 +++++ 2 files changed, 8 insertions(+) diff --git a/Contest_API.md b/Contest_API.md index e2b50c7c..b37ece39 100644 --- a/Contest_API.md +++ b/Contest_API.md @@ -1839,6 +1839,9 @@ Properties of run objects: | contest\_time | RELTIME | Contest relative time when run completed. | run\_time | number | Run time in seconds. Should be a non-negative integer multiple of `0.001`. The reason for this is to not have rounding ambiguities while still using the natural unit of seconds. +A CCS should create each run object as soon as it is ready. +This will for example allow clients to track judging progress in real-time. + #### Examples Request: diff --git a/Contest_Control_System_Requirements.md b/Contest_Control_System_Requirements.md index d92e0c0b..13ee3e12 100644 --- a/Contest_Control_System_Requirements.md +++ b/Contest_Control_System_Requirements.md @@ -990,6 +990,11 @@ return from the `/access` endpoint: } ``` +Furthermore, the CCS must satisfy the following: + +- It must publish [run](contest_api#runs) objects in real-time, so + that ICPC-Live can track and publish judging progress. + #### Access Restrictions