non-obvious choices in std IPv6 test creation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
We make a bunch of devices with a scope_id of 0, but the value of 0 is a reserved scope_id. I believe it's usually ignored or treated as equivalent to "eh whatever", but we probably should be making them with scope_id: 1, i.e. "entirely local to here". This prompted https://github.com/rust-lang/rust/pull/137967 because AIX helpfully fixes the value of scope_id to the one it interprets it as: 1.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with library/std/src/net/udp/tests.rs at the IPv6 test setup described in the issue. Review the devices created with scope_id: 0, update the relevant values to 1, and run the associated Rust standard-library networking tests to confirm the expected behavior, including the AIX-related case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100