Hello, First, thanks for the updates to domjudge.org/demoweb. It's nice to have a recent version of DOMjudge up on there to test against! Two URLs don't seem to work after this: * https://www.domjudge.org/demoweb/api/contests/5/scoreboard (500 Internal Error) * https://www.domjudge.org/demoweb/public/ ("lib/relations.php missing") The first one is quite important to me because I want to test against it with a resolver thingy I've been working on; the second one is probably quite important to new users poking around. Are the team already aware these are broken? Thanks, Robin
Hi Robin, It seems the first thing is broken because of the event_id / time / contest_time fields in the new 2019 API format: https://clics.ecs.baylor.edu/index.php?title=Contest_API_2019#Scoreboard_for... <https://clics.ecs.baylor.edu/index.php?title=Contest_API_2019#Scoreboard_format> Our demoweb doesn’t have any events and thus it breaks the code. I’d say under normal circumstances this shouldn’t happen (creating the contest will be the first event so there is always one…) but I’m not sure what the best way to fix demoweb is. Maybe others have an idea? The lib/relations.php missing thing is something for someone who better understands our Makefile process. I’m not sure why it is missing. By the way, if you just need an instance to talk to, we still have the NWERC judge up and running and you can probably talk to that. If you need info from it, ping me on the NWERC slack. Nicky
On 24 Dec 2018, at 10:29, Robin Lee <rglee32@gmail.com> wrote:
Hello,
First, thanks for the updates to domjudge.org/demoweb. It's nice to have a recent version of DOMjudge up on there to test against!
Two URLs don't seem to work after this:
* https://www.domjudge.org/demoweb/api/contests/5/scoreboard (500 Internal Error) * https://www.domjudge.org/demoweb/public/ ("lib/relations.php missing")
The first one is quite important to me because I want to test against it with a resolver thingy I've been working on; the second one is probably quite important to new users poking around.
Are the team already aware these are broken?
Thanks, Robin _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
On Mon, December 24, 2018 12:27, Nicky Gerritsen wrote:
Hi Robin,
It seems the first thing is broken because of the event_id / time / contest_time fields in the new 2019 API format: https://clics.ecs.baylor.edu/index.php?title=Contest_API_2019#Scoreboard_for... <https://clics.ecs.baylor.edu/index.php?title=Contest_API_2019#Scoreboard_format> Our demoweb doesnât have any events and thus it breaks the code.
I'd say under normal circumstances this should't happen (creating the contest will be the first event so there is always on...) but I'm not sure what the best way to fix demoweb is. Maybe others have an idea?
Demoweb is a snapshot of a database that we reload nightly. So the fix is to just add some appropritate events to that database snapshot? Cheers, Thijs
On 24/12/2018 14:23, Thijs Kinkhorst wrote:
On Mon, December 24, 2018 12:27, Nicky Gerritsen wrote:
Hi Robin,
It seems the first thing is broken because of the event_id / time / contest_time fields in the new 2019 API format: https://clics.ecs.baylor.edu/index.php?title=Contest_API_2019#Scoreboard_for... <https://clics.ecs.baylor.edu/index.php?title=Contest_API_2019#Scoreboard_format> Our demoweb doesnât have any events and thus it breaks the code.
I'd say under normal circumstances this should't happen (creating the contest will be the first event so there is always on...) but I'm not sure what the best way to fix demoweb is. Maybe others have an idea?
Demoweb is a snapshot of a database that we reload nightly. So the fix is to just add some appropritate events to that database snapshot?
I think it's better (and probably easier) to replace the current data that is from NWERC 2007 by data from a more recent contest, say NWERC 2018. Nicky, do you think that would be OK with Mart and Kevin? We'd strip all team sources and personal data. Jaap
I think that’s ok, but I have cc’ed them so if they have any objections or questions they will hopefully let this know. Nicky Sent from my iPhone
On 24 Dec 2018, at 21:11, Jaap Eldering <jaap@jaapeldering.nl> wrote:
On 24/12/2018 14:23, Thijs Kinkhorst wrote:
On Mon, December 24, 2018 12:27, Nicky Gerritsen wrote: Hi Robin,
It seems the first thing is broken because of the event_id / time / contest_time fields in the new 2019 API format: https://clics.ecs.baylor.edu/index.php?title=Contest_API_2019#Scoreboard_for... <https://clics.ecs.baylor.edu/index.php?title=Contest_API_2019#Scoreboard_format> Our demoweb doesnât have any events and thus it breaks the code.
I'd say under normal circumstances this should't happen (creating the contest will be the first event so there is always on...) but I'm not sure what the best way to fix demoweb is. Maybe others have an idea?
Demoweb is a snapshot of a database that we reload nightly. So the fix is to just add some appropritate events to that database snapshot?
I think it's better (and probably easier) to replace the current data that is from NWERC 2007 by data from a more recent contest, say NWERC 2018.
Nicky, do you think that would be OK with Mart and Kevin? We'd strip all team sources and personal data.
Jaap _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel
participants (4)
-
Jaap Eldering -
Nicky Gerritsen -
Robin Lee -
Thijs Kinkhorst