Checkpoints don't save until the evaluations are done
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 66
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Evaluations take almost 2 days, so better to have the checkpoints beforehand
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files or tests. Trace the checkpoint-saving and evaluation flow to determine where checkpoints wait for evaluations to finish; done means checkpoints are available before the evaluations complete, while preserving the existing evaluation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100