-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Hyper uses featured functions from socket2
without explicitly requiring it
#3045
Labels
C-bug
Category: bug. Something is wrong. This is bad!
Comments
Should be fixed via #3047 |
seanmonstar
added a commit
that referenced
this issue
Nov 7, 2022
Fix confirmed ! Kudos @LucioFranco && @seanmonstar 👍 |
papey
added a commit
to papey/scaphandre
that referenced
this issue
Nov 8, 2022
papey
added a commit
to papey/scaphandre
that referenced
this issue
Nov 10, 2022
papey
added a commit
to papey/scaphandre
that referenced
this issue
Feb 11, 2023
papey
added a commit
to papey/scaphandre
that referenced
this issue
Mar 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
As a transitive dependency from another crate, I get
hyper = "0.14.22"
, and thensocket2 = "0.4.7"
.Platform
Description
When a project adds hyper as a transitive dependency, some required features for
socket2
are missing, and my project wont compile.I tried this code:
Cargo.lock
:I expected to see this happen:
cargo build
without issueInstead, this happened:
It leads to those lines or this doc in socket2.
With the mention of :
On the function used in hyper
tcp.rs
.Adding socket2 as a dep with the the
all
feature in myCargo.toml
file solve the issue :but it's far from ideal and I think that it should be enabled on hyper side. I can work on the PR if you want.
Thanks 👍
The text was updated successfully, but these errors were encountered: