Feat/prevent forecast resubmission setting #3477
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
if no resubmission is allowed, all forecasts have infinite duration
lsabor
had a problem deploying
to
testing_env
GitHub Actions
Failure
lsabor
had a problem deploying
to
testing_env
GitHub Actions
Failure
lsabor
had a problem deploying
to
testing_env
GitHub Actions
Failure
lsabor
had a problem deploying
to
testing_env
GitHub Actions
Failure
lsabor
had a problem deploying
to
testing_env
GitHub Actions
Failure
lsabor
had a problem deploying
to
testing_env
GitHub Actions
Failure
lsabor
had a problem deploying
to
testing_env
GitHub Actions
Failure
lsabor
had a problem deploying
to
testing_env
GitHub Actions
Failure
lsabor
had a problem deploying
to
testing_env
GitHub Actions
Failure
…nt-forecast-resubmission-setting
hlbmtc
reviewed
Oct 15, 2025
…nt-forecast-resubmission-setting
…nt-forecast-resubmission-setting
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I've received product's approval for this. Ready for review and merge
closes https://github.com/Metaculus/auto-questions/issues/25
adds a field to the Project model which optionally disallows users to submit a second forecast after they've submitted one.
This also prevents withdrawal, and sets the submitted forecast's duration to infinite
In general, this feature will only be used in bot tournaments, so the UI aspect is of tertiary importance. Thusly, I've ignored fiddling with the "set forecast duration" elements and instead it just overwrites the duration to inifinite at the data level after receiving the forecast.