Report only gets written at the end of the recipe execution
Open
- Dominant language
- Python
- Stars
- 3
- Forks
- 1
- Avg merge
- 3m
- Merged PRs (30d)
- 5
Description
The report should be written to disk at the end of every step. Otherwise, if a recipe crashes, you lose any data you may have produced until that point.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing where the report is written during recipe execution and how the execution loop advances between steps. Ensure the report is persisted after every step, then verify that data from completed steps remains available when a later step crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100