Repository: Cloud-CV/EvalAI
Issue: Submission issues with server response 502 and "TypeError: response.input_file is undefined"
Root cause: Interface Contract Mismatch

Hi,
Since yesterday we have had consistent issues with submitting via the web interface.
Trying to submit causes the following server response in Firefox 128.7.0esr (similar in Edge) when running https://eval.ai/api/jobs/challenge/2453/challenge_phase/4859/submission/

![Image](https://github.com/user-attachments/assets/1e7a6ac6-158c-4051-a412-8f6cacf038ab)

and the following error message:
TypeError: response.input_file is undefined
    onError https://eval.ai/dist/js/controllers.min.js?t=1740990111641:1
    k https://eval.ai/dist/vendors/vendor.js?t=1740990111641:140
    $digest https://eval.ai/dist/vendors/vendor.js?t=1740990111641:151
    $apply https://eval.ai/dist/vendors/vendor.js?t=1740990111641:155
    k https://eval.ai/dist/vendors/vendor.js?t=1740990111641:105
    V https://eval.ai/dist/vendors/vendor.js?t=1740990111641:111
    onload https://eval.ai/dist/vendors/vendor.js?t=1740990111641:111
    Cg https://eval.ai/dist/vendors/vendor.js?t=1740990111641:111
    t https://eval.ai/dist/vendors/vendor.js?t=1740990111641:107
    b https://eval.ai/dist/vendors/vendor.js?t=1740990111641:105
    k https://eval.ai/dist/vendors/vendor.js?t=1740990111641:140
    $digest https://eval.ai/dist/vendors/vendor.js?t=1740990111641:151
    $apply https://eval.ai/dist/vendors/vendor.js?t=1740990111641:155
    compile https://eval.ai/dist/vendors/vendor.js?t=1740990111641:293
    dispatch https://eval.ai/dist/vendors/vendor.js?t=1740990111641:2
    handle https://eval.ai/dist/vendors/vendor.js?t=1740990111641:2
 Possibly unhandled rejection: {} [vendor.js:128:108](https://eval.ai/dist/vendors/vendor.js?t=1740990111641)
    e https://eval.ai/dist/vendors/vendor.js?t=1740990111641:128
    get https://eval.ai/dist/vendors/vendor.js?t=1740990111641:98
    g https://eval.ai/dist/vendors/vendor.js?t=1740990111641:139
    $digest https://eval.ai/dist/vendors/vendor.js?t=1740990111641:151
    $apply https://eval.ai/dist/vendors/vendor.js?t=1740990111641:155
    k https://eval.ai/dist/vendors/vendor.js?t=1740990111641:105
    V https://eval.ai/dist/vendors/vendor.js?t=1740990111641:111
    onload https://eval.ai/dist/vendors/vendor.js?t=1740990111641:111
    (Async: EventHandlerNonNull)
    Cg https://eval.ai/dist/vendors/vendor.js?t=1740990111641:111
    t https://eval.ai/dist/vendors/vendor.js?t=1740990111641:107
    b https://eval.ai/dist/vendors/vendor.js?t=1740990111641:105
    k https://eval.ai/dist/vendors/vendor.js?t=1740990111641:140
    $digest https://eval.ai/dist/vendors/vendor.js?t=1740990111641:151
    $apply https://eval.ai/dist/vendors/vendor.js?t=1740990111641:155
    compile https://eval.ai/dist/vendors/vendor.js?t=1740990111641:293
    dispatch https://eval.ai/dist/vendors/vendor.js?t=1740990111641:2
    handle https://eval.ai/dist/vendors/vendor.js?t=1740990111641:2

Hi @rikardvinge , Is this issue resolved?

Hi @RishabhJain2018, the issue for that challenge is not yet resolved, I still get the same error message and the submission is not uploaded.

However, since we are using a remote worker setup with a fork from the EvalAI-Starters repo, we tested to create a new challenge on [eval.ai](https://eval.ai/) and push our code to this new one instead. On the new challenge, submissions works as intended.

So from a challenge organization point of view, we can use the new challenge instead (although it needs to be approved before it goes live on Monday, right?), even though the issue persists on the old version.

I see..can you please send us the contact message with new the old and new challenge IDs? I can look into this!

For now, I am closing this issue, since it is resolved and your challenge works.

Thank you! Challenge IDs have been sent via EvalAI contact form.

just for the purpose of documentation:

- https://eval.ai/web/challenges/challenge-page/2465 (submission working)
- https://eval.ai/web/challenges/challenge-page/2453 (submission not working)

Thx, @RishabhJain2018 for all support!