worker (?): JWT worker validation fails
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
This may not be a worker issue exactly, but it's certainly affecting the worker
We had a lost run caused by a JWT error:
nbf is "not before". So that suggests that the worker has claimed a run early? Before the JWT allows it too? Wierd.
Rory says this occurred after a pod restart. Is it something weird about a new pod starting up?
This seems to be the only occurrence of this in the last 30 days
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 worker's JWT validation around the reported nbf error, then compare the GCP logs for global-worker before and after the pod restart. Done means explaining why the worker accepted or claimed the run too early and preventing the JWT failure from causing a lost run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100