Back to Signal Feed
CodeTracked since May 19, 2026

Reject duplicate incoming port entries during mirrord config validation

mirrord now rejects duplicate entries in incoming `port_mapping` and `listen_ports` before config processing continues, returning a clear duplicate-port error instead of accepting the config and silently dropping one mapping.

mirrord-configport_mappinglisten_portsBiMap

What Happened

  • mirrord now rejects duplicate entries in incoming `port_mapping` and `listen_ports` before config processing continues, returning a clear duplicate-port error instead of accepting the config and silently dropping one mapping.
  • mirrord now rejects duplicate entries in incoming `port_mapping` and `listen_ports` before config processing continues, returning a clear duplicate-port error instead of accepting the config and silently dropping one mapping.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

added a pre-check for duplicate source/target ports in `port_mapping` and `listen_ports` so conflicting network mappings are rejected during config generation with an explicit validation error.

Why Track This

Why It Matters

Operators and developers configuring mirrord now get immediate, explicit feedback when a port is duplicated in `port_mapping` or `listen_ports`, which helps prevent hidden forwarding misconfigurations and missing routes during debugging or development sessions. The previous behavior depended on `BiMap` semantics that kept only one of the duplicates, so one intended mapping vanished without warning; now the failure is deterministic and visible. Next, watch for whether any valid workflows rely on duplicate-like definitions and ensure CI/error surfaces continue to block only truly conflicting configs.

Impact

Operators and developers configuring mirrord now get immediate, explicit feedback when a port is duplicated in `port_mapping` or `listen_ports`, which helps prevent hidden forwarding misconfigurations and missing routes during debugging or development sessions. The previous behavior depended on `BiMap` semantics that kept only one of the duplicates, so one intended mapping vanished without warning; now the failure is deterministic and visible. Next, watch for whether any valid workflows rely on duplicate-like definitions and ensure CI/error surfaces continue to block only truly conflicting configs.

What To Watch Next

  • Watch whether mirrord-config becomes a repeated pattern.
  • Track follow-up changes around LLMOps.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: duplicate_port_checks_only_for_incoming_network_fields, false_positive_reports_with_intended_aliasing.
Open Topic TimelineOpen Technical EventOpen Original Sourceduplicate_port_checks_only_for_incoming_network_fields / false_positive_reports_with_intended_aliasing / validation_visibility_in_automation_pipelines

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

metalbear-co/mirrord PR #4276: Reject duplicate incoming port mappings

One duplicate port in `incoming.port_mapping` previously could be accepted, with `BiMap` keeping only one entry and dropping the other; the change makes config generation fail fast with a duplicate-port message.