Failure and input readiness entangled
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 8
- Forks
- 1
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 21
Description
When I have a failed node and try to run again, I get the error message:
The following node require inputs before you can run the graph:
Since I broke the node on purpose, I know which one it is and I can go hit the "reset" button (🚀 🚀 🚀 ), re-run, and everything is fine. I'm actually quite happy that running when there is a failed child is triggering a sort of controlled error message, but the message itself just needs to disentangle missing-input and actually-failed nodes and list them all. Direct users to the "reset" button right in the message would probably also be worthwhile.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the failure by running the graph after deliberately breaking a node, then run it again without resetting. Inspect how the error message distinguishes missing-input nodes from failed nodes. Done means the message lists both categories accurately and directs users to the reset button for failed nodes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100