Skip to content
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

log: don't enable this feature by default #660

Merged
merged 1 commit into from
Apr 14, 2022

Conversation

Noah-Kennedy
Copy link
Contributor

Unfortunately, tracing/log is a non-additive feature (tokio-rs/tracing#1793), so enabling it is a bit radioactive.

Unfortunately, tracing/log is a non-additive feature (tokio-rs/tracing#1793), so enabling it is a bit radioactive.
Copy link
Member

@davidpdrsn davidpdrsn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@hawkw what do you think?

Copy link
Member

@hawkw hawkw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that most people using Tower are probably also using tracing at this point, so I'm fine with removing the log support.

However, there's definitely an argument that this should be considered a breaking change. Although it shouldn't cause compilation to break, it does mean that log records from tower may suddenly disappear for any users who are (a) using log and (b) not enabling the tracing/log feature themselves. On the other hand...I don't actually care very much. I just thought this was worth bringing up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants