worker: show better error when OOMkilled during compilation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
When the a run gets killed due to using too much memory in compilation, the error the user gets is not very clear
What can we do about this?
-the worker could pronably detect the oom kill before run start, and so attach an appropriate error
-we can now put out more useful logs, eg "compilation started", "compilation complete in 10ms" etc. This is generally a good idea
- We should also ensure that compilation logs are debug level. Maybe. This affects CLI AND worker. Mixed feelings about hiding that stuff, but in the app it doesn't feel very relevant for most users
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 how the worker and CLI handle compilation failures and where compilation logs are emitted. Compare the possible approaches in the issue, then define the expected OOM error and logging behavior for both worker and CLI before making a change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100