You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge torrust#919: Fix: clients output in JSON should not include logging
2518c54 fix: [torrust#917] clients output in JSON should not include logging (Jose Celano)
Pull request description:
The console clients' output should not include logging info when the output is JSON. IT fixes this behavior:
Command:
```s
$ cargo run --bin udp_tracker_client announce 144.126.245.19:6969 9c38422213e30bff212b30c360d26f9a02136422
Finished `dev` profile [optimized + debuginfo] target(s) in 0.09s
Running `target/debug/udp_tracker_client announce '144.126.245.19:6969' 9c38422213e30bff212b30c360d26f9a02136422`
Output:
```s
2024-06-26T07:46:10.051490Z INFO torrust_tracker::console::clients::udp::app: logging initialized.
{
"AnnounceIpv4": {
"transaction_id": -888840697,
"announce_interval": 300,
"leechers": 0,
"seeders": 1,
"peers": []
}
}
```
The line `2024-06-26T07:46:10.051490Z INFO torrust_tracker::console::clients::udp::app: logging initialized.` or any other lines should not be included. I will open a discussion about how to deal with logging in console clients.
ACKs for top commit:
josecelano:
ACK 2518c54
Tree-SHA512: 9882e3b1701ce13549c8dd6c7a5a515bbdd8e3206eb560424c2e205962d2c50314d03f2ae19eed303aea1277d49b9a669a5d9f24701ac7631608850a0290667f
0 commit comments