feat: enable console subscriber layer for tracing spawn tasks on 127.0.0.1:6669
when log level is TRACE
#1275
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request introduces improvements to tracing and debugging capabilities, updates dependency versions, and addresses a double-decompression issue in HTTP downloads. The most significant changes are grouped below:
Tracing and Debugging Enhancements
console-subscriber
dependency todragonfly-client
and enabled the console tracing layer when log level is set to TRACE, allowing for better visibility into spawned tasks during debugging. (dragonfly-client/Cargo.toml
,dragonfly-client/src/tracing/mod.rs
) [1] [2]tokio
dependency to include thetracing
feature, and added configuration to enabletokio_unstable
for advanced runtime features. (Cargo.toml
,.cargo/config.toml
) [1] [2]tokio-console
binary in both release and debug images, improving runtime introspection for deployed containers. (ci/Dockerfile
,ci/Dockerfile.debug
,ci/Dockerfile.dfinit
) [1] [2] [3] [4] [5] [6] [7]Dependency and Version Updates
1.0.9
to1.0.10
for consistency and release tracking. (Cargo.toml
) [1] [2]HTTP Download Reliability
dragonfly-client-backend/src/http.rs
) [1] [2]Related Issue
Motivation and Context
Screenshots (if appropriate)