`warn!` output is invisible unless `RUST_LOG` is set
Maintainers usually reply within 2 days
Assessment
This issue has not been assessed yet.
Description
The PR does point at a real problem though. Even on master nothing is logged unless RUST_LOG is set, because env_logger defaults to the error level, so the mainnet warning never reaches the user:
$ bdk-cli --network=bitcoin wallets
Error: Generic error: No wallets configured yet.
$ RUST_LOG=info bdk-cli --network=bitcoin wallets
[2026-10-14T11:23:11Z WARN bdk_cli] This is experimental software and not currently recommended for use on Bitcoin mainnet, proceed with caution.
Error: Generic error: No wallets configured yet.
Originally posted by @vadim-anfv in https://github.com/bitcoindevkit/bdk-cli/issues/336#issuecomment-6167790881
The mainnet notice is just the easiest one to show. It applies to every warn! in the codebase, and those fire when something has already gone wrong, so a plain run stays silent about problems the code did notice.
My take is that showing warnings by default would be more user friendly, with RUST_LOG left as a way to change that default rather than a prerequisite for seeing a warning.
@tvpeter what do you think about changing the default this way?
- Dominant language
- Rust
- Stars
- 142
- Forks
- 103
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from bitcoindevkit/bdk-cli
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
bitcoindevkit/bdk-cli#360 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bitcoindevkit/bdk-cli#358 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bitcoindevkit/bdk-cli#357 ·
Maintainers usually reply within 2 days
-
Remove "wallet" field from `WalletConfigInner`Possibly taken @Jennycj claimed this 6 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bitcoindevkit/bdk-cli#332 · 2 comments ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
bitcoindevkit/bdk-cli#359 ·
Maintainers usually reply within 2 days
All issues in bitcoindevkit/bdk-cli
Similar issues
-
Make major, minor, and makedev safe on solarish targetsPossibly taken @xtqqczze claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Proxy ignores l5d-retry-http and l5d-retry-grpc conditions that follow a comma and spacePossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 3 days
-
sncast panics when decoding a `u384` valuePossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
foundry-rs/starknet-foundry#4635 ·
Maintainers usually reply within 3 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
crmne/omastats#31 · 1 reaction ·
Maintainers usually reply within 1 day
-
area:desktop priority:p2 type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day