-
Notifications
You must be signed in to change notification settings - Fork 689
feat: Get tcp_info
structure
#2615
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
Open
b-parikh
wants to merge
4
commits into
nix-rust:master
Choose a base branch
from
b-parikh:tcp-info
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
daaa9af
feat: Get `tcp_info` structure
b-parikh 7e6cd7e
chore: CHANGELOG entry for TCP_INFO sockopt addition
b-parikh 46c7bb0
Update changelog with pull request 2615
b-parikh 7cb4426
Revert "chore: CHANGELOG entry for TCP_INFO sockopt addition"
b-parikh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Added `TCP_INFO` sockopt to read TCP socket information on _linux_. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
Hi there
If uClibc has that symbol, you can add it to the libc crate. Otherwise, we need to filter it out:
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.
Added
tcp_info
to the uClibc symbols in libc: rust-lang/libc@4a34937. It looks like the CI still isn't happy though, do you know if that's because the libc change isn't published to crates.io yet?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.
That PR rust-lang/libc#4347 added it to the main branch, Nix uses the
libc-0.2
branch, so you need to ask the maintainer to backport it to this branch.Once the backport PR gets merged, update the
Cargo.toml
file to use it from git:nix/Cargo.toml
Line 31 in ea012be
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.
Got it, thanks! I'll update this PR when the change is backported.
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.
I'm a bit confused by this comment. The commit was backported to the 0.2 branch: rust-lang/libc@5a1f5f2. Why would pinning the version of the crate in the nix Cargo.toml file be the correct approach? I don't think that should get committed, right?
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.
Emm, I don't think I understand what you mean, could you please elaborate a bit?