Worker: better logging (and better handling?) when JWT expires
Open
Nobody has claimed this yet.
DevX
lost
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
I think we can lose runs if a JWT expires between claim and joining the run channel. Need to better understand the conditions
I'm sure I can at least log better
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 file or test is named; start by locating the worker flow that claims a run and joins its run channel, then review the linked Slack thread for the JWT-expiry conditions. Done should include useful logging for the expiry path, while the required handling change still needs to be defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100