Worker: sometimes sends events without a step id
Open
Nobody has claimed this yet.
DevX
lost
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Strange sequence of events in worker logs:
[SRV] ✘ cf698f95-4b16-4a75-9ac4-98e1729f7017 :: step:complete :: ERR: [step:complete] {"step_id":["This field can't be blank."]}
[SRV] ℹ cf698f95-4b16-4a75-9ac4-98e1729f7017 :: run:log :: OK
[SRV] ✘ cf698f95-4b16-4a75-9ac4-98e1729f7017 :: step:start :: ERR: [step:start] {"job_id":["does not exist"]}
[SRV] ✘ cf698f95-4b16-4a75-9ac4-98e1729f7017 :: run:log :: ERR: [run:log] {"step_id":["must be associated with the run"]}
How is step_id blank?
This should lead to lost. I think this run might recover, but interestingly there is a lost run (ea330df2-6b88-4cb3-84b9-4619e5d3c319) at almost the same time as this. Coincidence?
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 the linked GCP logs for run cf698f95-4b16-4a75-9ac4-98e1729f7017 and compare them with lost run ea330df2-6b88-4cb3-84b9-4619e5d3c319; trace the worker's step:start, step:complete, and run:log sequence. Done means the cause of the missing step_id or job_id is reproduced and invalid events no longer lead to a lost run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100