Worker: shouldn't compile log be debug info
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
When looking at logs with info on, do I really want to see compile times for each step? I... I don't think so
Part of the problem is we really only have "everything", "info" (whatever that means) and "bare minumum".
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's compile-time logging entry point and inspect how the existing info and debug levels are selected; the payload names no file or test. Done means compile timings no longer appear at info level while remaining available as debug output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100