Antlog issue

Please post all questions and answers in here. This way people can easily see if someone else has the same problem.

Moderators: petec, administrator, BeligerAnt

Post Reply
User avatar
Spaceman
Posts: 150
Joined: Wed May 14, 2014 3:16 pm
Location: Oxfordshire

Antlog issue

Post by Spaceman » Wed Oct 17, 2018 3:16 pm

Good afternoon.

I have set up AWS 57 on ant log, and I have seemed to have locked the database.

Is it broken, or have I broken it?

Could someone take a look who knows please?

Thanks
Team 1202

User avatar
BeligerAnt
Posts: 2458
Joined: Wed May 15, 2002 12:00 am
Location: Brighton
Contact:

Re: Antlog issue

Post by BeligerAnt » Wed Oct 17, 2018 9:36 pm

My guess is that you downloaded the database after you created the event. The intent is that it only locks if you are the owner of an imminent event (i.e. one where the online registration is closed, but there may be a slight flaw in the logic. That or someone else managed to lock it.

I'll take a look and unlock it, no worries.

PS I took a look at the database and you are not the culprit :) It was Razerdave who locked the database, so it looks like the logic worked properly as he is the owner of AWS56 which was in the correct state to cause the database to lock.

The database has to be locked while an event is running to prevent horrible problems if new teams/robots are created online and at the event.
Gary, Team BeligerAnt

User avatar
BeligerAnt
Posts: 2458
Joined: Wed May 15, 2002 12:00 am
Location: Brighton
Contact:

Re: Antlog issue

Post by BeligerAnt » Sat Oct 20, 2018 7:53 pm

The results of AWS56 have been uploaded and the database unlocked. Normal service has been resumed :)
Gary, Team BeligerAnt

User avatar
Spaceman
Posts: 150
Joined: Wed May 14, 2014 3:16 pm
Location: Oxfordshire

Re: Antlog issue

Post by Spaceman » Tue Oct 23, 2018 6:49 am

Another issue.

in AWS 57, Robototron has decided to enter himself into his own group all ready. pretty sure thats not right...
Team 1202

Post Reply