Hi guys
We're running domjudge 5.1.1 and for some reason I don't understand we're being plagued this year by errors like the following:
error: Error while executing curl POST to url http://domserver.cosc.canterbury.ac.nz/api/judging_runs: http status code: 500, response: error: SQL error, Error#1264: Out of range value for column 'totaltime' at row 1, query: 'REPLACE INTO scorecache_public (cid, teamid, probid, submissions, pending, totaltime, is_correct) VALUES (24,1403,222,1,0,-15780,1)'
They occur when you set up a contest with an early opening date for testing purposes, make submissions then, later, move the opening date forward to the correct time. Refreshing the cache then results in those errors (because the submission time relative to the contest start time is negative), crashing the judgehosts. I've been solving the problem by marking the early submissions as "IGNORE this submission" or by hacking at the database directly but neither of those workarounds is very satisfactory. I don't recall having these errors last year, and nor do I think I've upgraded domjudge system since then, though I might have upgraded the OS? Any suggestions for a better work around, please?
Richard
Hi Richard,
This is indeed an issue we ourselves have also run into, precisely as you described.
In master we fixed it by removing the "unsigned" attribute from the table fields, see: https://github.com/DOMjudge/domjudge/commit/8be3edebbf9ca1314c57f669000cb403...
It means that the submissions can show up with negative penalty time, but I think that's ok, given that this should only occur for jury submissions that should not be publicly visible.
Best, Jaap
On 12/07/17 07:38, Richard Lobb wrote:
Hi guys
We're running domjudge 5.1.1 and for some reason I don't understand we're being plagued this year by errors like the following:
error: Error while executing curl POST to url http://domserver.cosc.canterbury.ac.nz/api/judging_runs: http status code: 500, response: error: SQL error, Error#1264: Out of range value for column 'totaltime' at row 1, query: 'REPLACE INTO scorecache_public (cid, teamid, probid, submissions, pending, totaltime, is_correct) VALUES (24,1403,222,1,0,-15780,1)'
They occur when you set up a contest with an early opening date for testing purposes, make submissions then, later, move the opening date forward to the correct time. Refreshing the cache then results in those errors (because the submission time relative to the contest start time is negative), crashing the judgehosts. I've been solving the problem by marking the early submissions as "IGNORE this submission" or by hacking at the database directly but neither of those workarounds is very satisfactory. I don't recall having these errors last year, and nor do I think I've upgraded domjudge system since then, though I might have upgraded the OS? Any suggestions for a better work around, please?
Richard
DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
Ah, a nice simple fix. I'll do that. Thanks Jaap.
Richard
On 13/07/17 01:57, Jaap Eldering wrote:
Hi Richard,
This is indeed an issue we ourselves have also run into, precisely as you described.
In master we fixed it by removing the "unsigned" attribute from the table fields, see: https://github.com/DOMjudge/domjudge/commit/8be3edebbf9ca1314c57f669000cb403...
It means that the submissions can show up with negative penalty time, but I think that's ok, given that this should only occur for jury submissions that should not be publicly visible.
Best, Jaap
-
Jaap Eldering -
Richard Lobb