-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default competition docker image updated, some competitions may be affected #3263
Comments
https://codalab.lisn.upsaclay.fr/competitions/7404#learn_the_details @Didayolo hi, could you help with this bug or should I contact coco team to fix this? thank you |
#3255 |
HO3D_v2 website is having problems again:https://codalab.lisn.upsaclay.fr/competitions/4318 |
We have currently a power outage in the whole district. The service will be back tomorrow and I'll do my best to solve this issue. |
Thanks for the feedback. OK so I guess I need to investigate to find which tag is the old default image. UPDATE: this is weird. The image I've set up was indeed the old default image. |
|
It was due to a power outage. It is back now. |
Hi, Indeed. Bad theory above but I'm working on it and will keep you informed. |
Got it. Many thanks! Looking forward to your update. |
Wow I think I understand what happened. The problem was indeed solved by reverting to the old docker image, but on your competition the organizers had upgraded their scoring program to match the new version of the docker image. So when I "fixed" it, I actually broke it because it was already solved in the meantime. Hopefully it should work now, please give me feedback @hxwork |
Just a remark, still about HO3D_v2. With the new scoring program and new competition docker image, it seems that the F1 score announced in the scoring logs are always 0. I don't want to touch the choice of scoring program for the organizers. If the organizers want to come back to last week behavior, they just need to select back the old scoring program and to put If the new behavior if fine, then everything is OK. |
Hi @Didayolo, I have tested the online evaluation and it works now. However, as you said that the F scores are always 0. Hope the organizers can fix this later. |
Yes, I can open the website normally. |
Yeah... I don't know which scoring program was used before so I can't make that change by myself... I think the best thing to do is to contact the organizers. They can simply put the old scoring program and codalab-legacy:py2 docker and everything should work as earlier. |
Hi @Didayolo, Looks like our competition may have been impacted too, could you please confirm and fix if needed? Thanks |
Indeed, as the "competition Docker image" field is blank in the editor, your competition is affected. The fix is simply to fill it with I've done it already, everything should be good. |
Thanks @Didayolo. I tried again this morning and it was still throwing the same error, so I tried uploading a new version of the scoring script and printing In any case I also pushed a change to the way I was writing to the output file, now using mode 'w' instead of 'wb' and that appears to have fixed the original error, so probably best to leave as is. Submissions runs appear to be taking much longer than usual though, hopefully that's just temporary. |
This is not normal. @danlou Quick question, for testing this morning did you re-upload submissions or re-run them using the "submissions" interface? When I try to re-upload one of your submission (not click on re-run), I can see this in the scoring logs:
Fixing your scoring program to use Python 3 is not a bad idea indeed as Python 2 is deprecated. If you want to run on Python 3, leave blank the field "competition docker image" in the editor. |
Ah, that's it then. I was re-running submissions from the Submissions page. Thanks for clarifying! |
Hi @Didayolo, Looks like the competition may have been impacted too, could you please confirm and fix it? Thanks problem as shown below |
Hi @Didayolo , |
Hi @Didayolo, this competition seems to have some problems, too. Could you please take a look? Thanks. https://codalab.lisn.upsaclay.fr/competitions/7403#participate-submit_results |
Done! |
I close this issue for now. As mentioned in the first message, the fix (if needed) is easy to perform as a challenge organizer. |
Hi @Didayolo , this competition seems to have the same problems. Could you please take a look? Thanks. |
This competition is indeed using the default image. If you are the competition organizer and you get similar errors, then you should change the Docker image:
Then you can re-submit to see if the problem is solved. Do not use the "re-run" option from the submissions panel, because it re-runs submissions using their original Docker image. I hope this helps. |
Hello,
We have recently updated the default competition docker image from
codalab/codalab-legacy:py2
tocodalab/codalab-legacy:py39
(see https://groups.google.com/g/codalab-competitions/c/ePhMJKpcDFM). This is the environment in which the submissions run if nothing is set by the organizers.I merge here all issues related to this problem: #3262, #3260, #3261, #3255, #3257 and more.
Please send me the URLs of affected competitions so I can solve the issue. Thank you.
The fix
Problems of retro-compatibility can be solved by manually setting the competition docker image to
codalab/codalab-legacy:py2
. This can be done by the organizers or by an administrator of the platform, using the editor. See the screenshot below:The text was updated successfully, but these errors were encountered: