Fix #4848: Prevent seed script crash in non-interactive environments #4850
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes a crash in the database seed process when EvalAI is run in non-interactive environments such as Docker or CI pipelines.
Problem
The
scripts/seed.pyscript prompts for user confirmation usinginput()when existing database data is detected.When executed in non-interactive environments (e.g. during
docker-compose up), this causes anEOFErrorand prevents the Django container from starting.Solution
Testing
docker-compose uplocally.Fixes #4848