Skip to content
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

Errors when updating the challenge template #82

Open
imprs opened this issue Feb 14, 2024 · 1 comment
Open

Errors when updating the challenge template #82

imprs opened this issue Feb 14, 2024 · 1 comment

Comments

@imprs
Copy link

imprs commented Feb 14, 2024

Hi,

I am getting the following errors when I update the challenge_config.yaml after using the given template initially. I understand the reasons behind some of these checks but at the same time, it is quite confusing that one can't change things even during the challenge development phase. It seems like a hard-requirement for the host to update the template in one go on the challenge branch otherwise these errors would start to pop up.

Following errors occurred while validating the challenge config:
ERROR: Challenge phase 2 not found in config. Deletion of existing challenge phase after challenge creation is not allowed.
ERROR: Dataset split 3 doesn't exist. Addition of a new dataset split after challenge creation is not allowed.
ERROR: Challenge phase split (leaderboard_id: 1, challenge_phase_id: 1, dataset_split_id: 2) doesn't exist. Addition of challenge phase split after challenge creation is not allowed.
ERROR: Challenge phase split (leaderboard_id: 1, challenge_phase_id: 1, dataset_split_id: 3) doesn't exist. Addition of challenge phase split after challenge creation is not allowed.
ERROR: Challenge phase split (leaderboard_id: 1, challenge_phase_id: 2, dataset_split_id: 2) not found in config. Deletion of existing challenge phase split after challenge creation is not allowed.
ERROR: Challenge phase split (leaderboard_id: 1, challenge_phase_id: 2, dataset_split_id: 1) not found in config. Deletion of existing challenge phase split after challenge creation is not allowed.
There was an error while creating an issue: 404 {"message": "Not Found", "documentation_url": "https://docs.github.com/rest/repos/repos#get-a-repository"}

Exiting the challenge_processing_script.py script after failure
@Liuziyu77
Copy link

Hi,

I am getting the following errors when I update the challenge_config.yaml after using the given template initially. I understand the reasons behind some of these checks but at the same time, it is quite confusing that one can't change things even during the challenge development phase. It seems like a hard-requirement for the host to update the template in one go on the challenge branch otherwise these errors would start to pop up.

Following errors occurred while validating the challenge config:
ERROR: Challenge phase 2 not found in config. Deletion of existing challenge phase after challenge creation is not allowed.
ERROR: Dataset split 3 doesn't exist. Addition of a new dataset split after challenge creation is not allowed.
ERROR: Challenge phase split (leaderboard_id: 1, challenge_phase_id: 1, dataset_split_id: 2) doesn't exist. Addition of challenge phase split after challenge creation is not allowed.
ERROR: Challenge phase split (leaderboard_id: 1, challenge_phase_id: 1, dataset_split_id: 3) doesn't exist. Addition of challenge phase split after challenge creation is not allowed.
ERROR: Challenge phase split (leaderboard_id: 1, challenge_phase_id: 2, dataset_split_id: 2) not found in config. Deletion of existing challenge phase split after challenge creation is not allowed.
ERROR: Challenge phase split (leaderboard_id: 1, challenge_phase_id: 2, dataset_split_id: 1) not found in config. Deletion of existing challenge phase split after challenge creation is not allowed.
There was an error while creating an issue: 404 {"message": "Not Found", "documentation_url": "https://docs.github.com/rest/repos/repos#get-a-repository"}

Exiting the challenge_processing_script.py script after failure

Same issue, did you solve it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants