rust-lang / rust-lang/rust-playground
Enhance backend logging to track more detailed information
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 267
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
We'd like to know what operations are actually run the most (e.g. build vs compile vs ASM vs Clippy...) and their options (mode, channel)
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
No files, tests, or entry points are named in the issue. Start by locating the backend logging and operation-dispatch code, then determine how build, compile, ASM, and Clippy options such as mode and channel are currently represented. Done means logs provide enough detail to identify operation frequency and those options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- analytics, backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100