Worker: report a good clear error if a websocket message timesout
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
If any worker -> lightning message times out on the websocket (ie because it took 10 seconds to reply), the run right now will be lost.
We can do better than this! We should surely be able to report the timeout somwhere, or continue retrying.
We may need help on the lightning side to recognise that message responses are slow.
Everyone will understand if the system is under load and running slow - so long as the work does get done eventually.
Probably the answer here is just to retry the message, or backoff and retry.
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
No files or tests are named. Start by tracing the worker-to-lightning websocket request and response timeout handling, then determine where a timed-out message causes the run to be lost. Done means the timeout is reported clearly or the message is retried with suitable backoff, including any required coordination with the lightning side.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100