oxidecomputer / oxidecomputer/crucible
allow binding downstairs to arbitrary port
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
by opening a socket on port 0, the OS will select an arbitrary open port for use and return that. rewrite the downstairs logic to support this use case (possibly also selecting an arbitrary repair port?). this will mean that the integration tests won't need to specify an arbitrary port manually, and will not impact the way the agent currently opens downstairs.
this may also address https://github.com/oxidecomputer/crucible/issues/261
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 by locating the downstairs logic that opens its socket and the integration tests that currently specify ports. Check how port 0 is reported after binding, and determine whether the repair port follows the same path. Done means downstairs can use an OS-selected port without changing the agent's current behavior, with integration tests no longer choosing a manual arbitrary port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100