worker: on socket error, report workflow complete (with crash exit)
Open
Nobody has claimed this yet.
DevX
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
When there's an error on a critical workflow event, the run will be a lost - which gives us all sorts of problems
Maybe what we need to do is stop the workflow at this point (? Can we even stop the runtime?) and send a complete-with-crash state to lightning
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 at packages/ws-worker/src/server.ts around line 319 and trace how critical workflow events handle socket errors. Determine how the runtime is stopped at that point and how the complete-with-crash state is sent to Lightning. Done means a socket error reports the workflow as complete with a crash instead of leaving the run lost.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100