Open jpbrunetsx opened 4 weeks ago
Hi, thank you for reporting this issue.
@ObadaS Do you think we have some kind of 24h timeout setting in MinIO?
Hello, The MinIO link in the error does seem to have an expiry date at the end. I think that links created by the code have a set expiry time which seems to be lower than 24 hours. I think you would need to alter something in the code to request a longer expiry.
I will continue searching on my side and will update this issue if I find something else.
I seem to have found the code that creates the URLs https://github.com/codalab/codabench/blob/1bd7c6fdb6f2e457187f6f6e6bb994f74e2cca1a/src/utils/data.py#L76
The duration is 24h, so it should be possible to change it there, or make it variable somehow https://github.com/codalab/codabench/blob/1bd7c6fdb6f2e457187f6f6e6bb994f74e2cca1a/src/utils/data.py#L46
Very nice catch. Should we simply put a higher limit? For instance 4 days? Or can this have bad consequences?
Could it be possible to link it to the competition ? So that they can decide to make it higher if needed (up to a hard limit of course) without having every link for all competitions be upgraded to 4 days since it's rarely needed
Should be fixed by #1659, soon to be deployed
Hi, In our competition we are running into an issue with failed submission with what appears to be a timeout. We did increase the running time to 72h in the task itself.
Competition : 3282 https://www.codabench.org/competitions/3282/ Exemple submission with a problem : 95068
Description: The submission fails after around 24h with the following error :
A shorter version running sub 24h does not trigger the issue.