worker: run goes into engine and vanishes?
Open
Nobody has claimed this yet.
DevX
lost
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Never seen this before:
- Run is claimed
- Compile, autoinstall, credential load all OK
- We call engine.execute
- Nothing else in the logs
- Run lost as not started
Debug logs may help (which are disabled on this run)
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 at the worker path that calls engine.execute and compare it with the linked GCP logs. Reproduce the disappearance with debug logging enabled, then trace what happens after engine.execute returns or fails. Done means the cause of the lost run is identified and the worker records or reports the outcome instead of silently losing it.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100