What to do if an edge condition throws?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
What happens if an edge condition throws? Either deliberately (which is silly but) or because of a logical error. This gets likely when we allow users to add their own conditions.
Right now in Lightning it'll Crash the attempt. If we're lucky users will see a log line associated with the run, probably the attempt. But if the attempt is close, lightning will reject the logs. So it's a bit of a crapshoot right now.
Probably what we want is for that edge to not get executed, but for the rest of the workflow to run? Oh I don't know, maybe the crash IS correct - just like we crash on a syntax error in a job.
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
Start by tracing how Lightning evaluates edge conditions and how an attempt records crashes and logs. Compare this behavior with syntax errors in jobs and consider the implications for user-defined conditions. Done requires a decided error-handling policy for failed edge conditions and a corresponding implementation and test plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100