Worker: better error logging on run error
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
run-error.ts might need to report to Sentry on error
Check this log for an example where there's an error, and we get no feedback in the logs, and sentry isn't notified.
It also looks like the worker leaves the socket after this? Maybe that needs to be on sentry too
it's worth searching GCP log for queue socket closed - it seems to happen quite a lot. What's causing it?
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 with run-error.ts and compare its error handling with the linked GCP log example. Search the worker code and GCP logs for "queue socket closed" to determine whether the socket event is related. Done means the relevant worker errors are visible in logs and reported to Sentry, with the socket-closure cause addressed if confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, typescript
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100