-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(pathfinder): add tokio-console non-default feature #179
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, just a small comment about tokio features
[dependencies] | ||
anyhow = "1.0.44" | ||
async-trait = "0.1.52" | ||
# paritys scale codec locks us here | ||
bitvec = "0.20.4" | ||
bytes = "1.1.0" | ||
clap = "2.33.3" | ||
console-subscriber = { version = "0.1.3", optional = true } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't the tracing
feature be enabled for tokio
too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good, just the tokio tracing feature as @CHr15F0x mentioned.
When building with this feature enabled pathfinder enables console_subscriber to expose tracing data for tokio-console. NOTE: as per the tokio-console documentation this also requires building with `tokio_unstable` for now, like: ``` RUSTFLAGS="--cfg tokio_unstable" Cargo build --features tokio-console ```
8004e7c
to
0395366
Compare
I think you can ignore the clippy for now. I've fixed it in my PR already. |
@kkovaacs pls merge 😉 |
When building with this feature enabled pathfinder enables console_subscriber
to expose tracing data for tokio-console.
NOTE: as per the
tokio-console
documentation this also requires buildingwith
tokio_unstable
for now, like: