Skip to content

refactor(net): finish the Hop rename in test names and log fields - #3264

Merged
kixelated merged 1 commit into
devfrom
claude/rename-peer-origin-tests
Sep 1, 2026
Merged

refactor(net): finish the Hop rename in test names and log fields#3264
kixelated merged 1 commit into
devfrom
claude/rename-peer-origin-tests

Conversation

@kixelated

Copy link
Copy Markdown
Collaborator

Follow-up to #3252, which renamed the hop identifier from Origin to Hop. That PR was scoped to the published surface and deliberately stopped there, so a few internal identifiers kept the old spelling.

  • Seven test functions still said peer_origin, sitting directly under the with_peer_hop / peer_hop API they exercise (moq-net: server.rs, lite/subscriber.rs, ietf/subscriber.rs, ietf/publisher.rs).
  • The cluster startup log emitted origin_id (moq-relay/src/cluster.rs). This is the one a reader could actually trip on: the value is origin.id(), a Hop, and every other hop id the relay reports now spells it hop_id — including GET /nodes, which refactor(net)!: name the hop identifier Hop, and fix three API shapes the review found #3252 renamed. The two disagreeing was a live inconsistency in operator-facing output, not just naming taste.
  • Two locals held a bare Hop under the name origin (server.rs, tests/goaway.rs). Note that most origin locals in these files are correct and untouched: they hold an origin::Producer from Hop::…().produce(), which is genuinely the routing table.

Also unchanged, for the same reason #3252 gave: origin::Producer's private info field still holds a Hop, and untangling it collides with a dozen sites where info is a local for the real Info.

No public surface moves, so this targets dev only because the rename it finishes lives there.

Verification

just check passed but dispatched no Rust step at all despite a diff of six rs/ files, so the Rust half was run directly against the same nix-store toolchain instead:

  • cargo clippy -p moq-net -p moq-relay --all-targets --locked -- -D warnings — clean
  • cargo nextest run -p moq-net -p moq-relay --locked1297 passed, 1 skipped
  • The 7 renamed tests confirmed present and passing under their new names (-E "test(peer_hop)"), so the rename didn't quietly orphan them

That just check skipped Rust here looks like a real bug in the diff-aware scoping rather than anything about this branch, and it's worth a look on its own — it means a Rust-only change can pass just check locally without being compiled. Filing separately.

(Written by Claude Opus 5)

The Hop rename left the identifier's old spelling in a few internal
identifiers: seven test functions still said peer_origin, the cluster
startup log emitted an origin_id field, and two locals held a bare Hop
under the name origin. None of these are published surface, so they were
left out of the rename that landed them.

The log field is the one a reader could trip on: every other hop id the
relay reports, including GET /nodes, now spells it hop_id.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 1, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-01T03:48:28.133543Z 7ffca72 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@kixelated
kixelated merged commit 544ef50 into dev Sep 1, 2026
3 checks passed
@kixelated
kixelated deleted the claude/rename-peer-origin-tests branch September 1, 2026 04:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant