Worker: handle events getting rejected by lightning
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
It seems that if Lightning rejects an event like step:complete, the worker doesn't do anything with it.
We need to add some logic here.
What should we do?
- if we continue to send other events, lightning will just reject them
- so maybe better to send an error event and just abort the run - mark it with Exception
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 the worker path that handles rejected Lightning events, using step:complete as the reproduction case. Read the existing run error handling around marking a run with Exception, and check any worker tests covering event delivery or failures. Done means the rejection has defined behavior, including whether later events stop and how the run is reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100