Skip to content

fix: use explicit address equality - #10257

Merged
ReubenBond merged 1 commit into
dotnet:mainfrom
ReubenBond:fix/silo-address-equality
Jul 13, 2026
Merged

ReubenBond merged 1 commit into
dotnet:mainfrom
ReubenBond:fix/silo-address-equality

Conversation

@ReubenBond

@ReubenBond ReubenBond commented Jul 9, 2026

Copy link
Copy Markdown
Member

Some address comparisons can bind to an unintended equality overload when written with == or !=. Use explicit Equals calls for IPAddress and SiloAddress comparisons across networking, placement, and diagnostics.

This PR is stacked on #10256 so the commits appear in the same order as the dissemination branch; merge the parsing PR first.

Microsoft Reviewers: Open in CodeFlow

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Use Equals for IPAddress and SiloAddress comparisons across networking, placement, and diagnostics so comparisons invoke the intended value equality overload.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 56caa2ba-bee6-450b-b29b-da02b0541333
@ReubenBond
ReubenBond force-pushed the fix/silo-address-equality branch from 4dc1ead to 61858ca Compare July 10, 2026 03:12
@ReubenBond
ReubenBond merged commit 71ec7b4 into dotnet:main Jul 13, 2026
62 checks passed
@ReubenBond
ReubenBond deleted the fix/silo-address-equality branch July 13, 2026 20:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant