Rethink error handling for fails
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
I've got some nasty spaghetti code between the runtime and the worker to handle fail cases.
The runtime emits an error message when a job fails. This is caught by the worker and triggers a job complete message.
But because of the way I'm trying to distinguish crash and fail, basically it gets ugly.
I think the runtime is doing the right thing, I probably just need to include severity and use that in the worker.
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 runtime error message flow into the worker's job-complete handling. Review how crash and fail cases are currently distinguished, then confirm the intended severity values and their effects. Done means the runtime and worker handle failures without the described duplicated or tangled logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100