worker: status API
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
Give the worker a REST API to return the status of either all runs, or just the requested run
Difficulty: can we cache this anywhere? If the worker is restarted then all history is lost
If we do cache, when should the cache be removed?
Do we need auth on top? Should we have a HTML interface?
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 mapping the worker's existing status and run lifecycle; the payload does not name files, tests, or entry points. Define what the REST API returns for all runs and a requested run, then resolve whether history is cached, when it is removed, whether authentication is required, and whether an HTML interface is in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100