microsoft / microsoft/demikernel

[inetstack] `0` Should Be Supported as the Wildcard Port

Open
#582 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug confirmed
Dominant language
Rust
Stars
1.2k
Forks
151
No merged PRs in 30d

Description

Description

The standard socket API normally accepts 0 as the wildcard port. We don't appear to support this currently.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name files or tests. Start by locating the inetstack socket bind path and its handling of port 0, then compare that behavior with the standard socket API; done means port 0 is accepted as the wildcard port.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.