-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix(examples): remove now missing tower feature #2427
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
Conversation
It was removed in hyperium#2339 Now clippy is unhappy about us requiring it in examples: ``` warning: invalid feature `tower` in required-features of target `tower-client`: `tower` is not present in [features] section warning: invalid feature `tower` in required-features of target `tower-server`: `tower` is not present in [features] section ```
|
Perhaps the right thing to do is to reintroduce it. cc @dfawley, @arjan-bal |
|
Possibly. @arjan-bal do you remember why you removed it? |
|
Hi @bobrik, thanks for reporting this. In #2339 I was running into issues with cargo udeps --no-default-features --features tower
error: package `grpc v0.9.0-alpha.1 (/path/to/tonic/grpc)` does not have feature `tower`
help: an optional dependency with that name exists, but the `features` table includes it with the "dep:" syntax so it does not have an implicit feature with that name
Dependency `tower` would be enabled by these features:
- `_runtime-tokio`This seems to be happening because cargo creates a feature for each optional dependency under the hood. When I try to add a feature named I'm unsure if this is a bug in I (incorrectly) assumed that the The correct fix would be to re-introduce the feature and keep the udeps check passing. @LucioFranco do you know how we could fix the problem I'm facing with udeps test? I have a PR (arjan-bal#7) with the commits which fail with the errors I mentioned above. |
|
oh oops I accidentally updated this PR with updates from main. @arjan-bal that is a good question, I honestly don't know the answer. I would say try to re-open that PR that re-introduces the feature and then we can get someone who knows the tool a bit better to help us. |
|
@LucioFranco raised a PR with the failing |
|
We can close this now as I have a fix in #2432 |
It was removed in #2339
Now clippy is unhappy about us requiring it in examples: