oxidecomputer / oxidecomputer/falcon
Migrate from slog to tracing.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 5
- Avg merge
- 11d 13h
- Merged PRs (30d)
- 2
Description
Slog itself recommends using tracing, so let's use tracing.
Also: slog env_looger is a bit derpy to set up with defaults that provide useful logging information for falcon CLI applications. In particular, the need to set the environment variable RUST_LOG with std::env::set_var is unsafe from multi-threaded code.
Hopefully, we can find a better path forward with tracing for user-configurable log levels with a useful default.
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 reading lib/src/lib.rs lines 252-261 and the issue's linked Rust documentation for std::env::set_var. Trace how slog and RUST_LOG are currently configured for Falcon CLI applications. Done means the logging approach uses tracing, supports user-configurable log levels safely, and retains useful defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100