https://github.com/josecelano/tracing-test-bug
Repo to reproduce a bug in the tracing-test crate
https://github.com/josecelano/tracing-test-bug
Last synced: 3 months ago
JSON representation
Repo to reproduce a bug in the tracing-test crate
- Host: GitHub
- URL: https://github.com/josecelano/tracing-test-bug
- Owner: josecelano
- Created: 2024-12-20T10:08:50.000Z (6 months ago)
- Default Branch: main
- Last Pushed: 2024-12-22T09:33:24.000Z (6 months ago)
- Last Synced: 2025-03-15T00:13:48.057Z (3 months ago)
- Language: Rust
- Size: 6.84 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Tracing Test Bug
This repo was created to reproduce a bug in the [tracing-test](https://github.com/dbrgn/tracing-test) crate.
When you run the application, you should see the following output:
```console
$ cargo run
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.02s
Running `target/debug/tracing-test-bug`
2024-12-20T09:56:43.725466Z INFO tracing_test_bug: level 1
2024-12-20T09:56:43.725551Z INFO tracing_test_bug: level 2
2024-12-20T09:56:43.725650Z INFO tracing_test_bug: level 3
```
The application has three levels of nested threads.
When you run the tests, logs are apparently only captured in the same thread.
## Links
- Issue on [tracing-test](https://github.com/dbrgn/tracing-test) repo: [No capture from std::thread::spawn or tokio::task::spawn_blocking]().