Fix: Error Message while validating Challenge Config #4490

[Shubhamx404]

@RishabhJain2018 @Shekharrajak

i actually solved issue of EvalAI repo issue #4490 , i made changes to (challenge_processing_script.py)

what was the issue?

Fix misleading error message when EvalAI auth token is expired during challenge validation

• While validating or creating a challenge on EvalAI using the GitHub Actions workflow, an expired or invalid EvalAI auth token results in a 401 Unauthorized response from the API.
• However, the current error handling:
• Assumes the API response always contains an "error" key
• Raises a misleading KeyError: 'error'
• Does not inform the user that the actual problem is an expired auth token
• This makes the failure confusing and difficult to debug for challenge hosts.

i actually solved issue of EvalAI repo issue #4490 , i made changes to (challenge_processing_script.py)

Solution

• Explicitly handling HTTP 401 Unauthorized responses from EvalAI
• Displaying a clear, actionable error message when the auth token is expired or invalid
• Avoiding unsafe access to response.json()["error"]
• Centralizing and hardening EvalAI HTTP error formatting
• Ensuring the GitHub Action fails cleanly with a helpful explanation

Please review my Pr @RishabhJain2018
Thanks
Shubham Kumar Sharma