MCJ Vasseur
MCJ Vasseur
As mentioned by @nickygerritsen in https://icpctools.slack.com/archives/C02GTS6EE2F/p1712382656158339?thread_ts=1712367696.875099&cid=C02GTS6EE2F, it seems we don't expose the points for a problem in the API.
It's reported as the progress in the current rejudging not how many repeated rejudgings left todo. ``` ID | reason | repetitions | startuser | finishuser | starttime | finishtime...
The time is picked from when the current (`i`th) rejudging started, not when the first (`0`th) rejudging started.
One can get this information by periodically polling the UI or API/Scoreboard. During the EUC this was asked for, personally I think it makes sense but I'm not sure if...
When we shadow PC^2 they use a relative URL starting with a `/`, the baseURL we use ends with a `/` which leads to problems. We tried by replacing the...
Closes: https://github.com/DOMjudge/domjudge/issues/2276
@nickygerritsen and me quickly looked that the found issues and they seem to be good to fix.
We had this discussion in the past and should revisit the idea to let `jury` users get the optional role to also upload the problems. - Should they be allowed...
Assume you want to mirror to domjudge.org, I think it makes sense to also give +x for other to make sure that the webserver can always access the `js` folder.
Normally we would need 2 button presses, 1 to start judging and the other after the `lazy` eval finished to go further. In case we shadow onDemand we are probably...