Resume from failure point
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 161
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
I have noticed that the execution graph is pickled.
Is there a plan for a way to resume a study execution from its last point of failure?
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
Start by locating the execution-graph pickling and failure-handling entry points; the issue names no files or tests. Define how a failed study should record its last completed point and how a later run should resume there, then add coverage showing that resume behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, hpc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100