Skip to content

Keep global transit tails out of fanout phases - #3986

Closed
ShiboSoftwareDev wants to merge 1 commit into
mainfrom
fix/fanout-phase-connection-scope
Closed

ShiboSoftwareDev wants to merge 1 commit into
mainfrom
fix/fanout-phase-connection-scope

Conversation

@ShiboSoftwareDev

Copy link
Copy Markdown
Contributor

Problem

The T113-S3 HDMI breakout produces a group-owned pad-to-boundary connection and a later global boundary-to-boundary connection with the same source_trace_id. The phase filter matched both through the source trace, so the fanout solver received the global transit tail even though that segment belongs to the later global phase.

Change

When an active routing group has an explicit connection for a source trace, its fanout phase now excludes the ungrouped sibling for that trace. If no group-owned split exists, the existing source-trace matching behavior remains unchanged.

The regression uses the exact 27-connection HDMI fanout input captured from the 96-component T113-S3 Linux board. Its SVG shows the blue global tail present before filtering and deferred after the fix.

Validation

  • bun test tests/repros/repro-t113-fanout-phase-transit.test.ts tests/utils/autorouting/phased-autorouting-bounds.test.ts tests/utils/autorouting/differential-pair-phase-filter.test.ts tests/repros/repro-shared-capacitor-breakout-handoff.test.tsx
  • 4 tests, 38 assertions
  • git diff --check origin/main...HEAD

@vercel

vercel Bot commented Sep 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
tscircuit-core-benchmarks Ready Ready Preview Sep 16, 2026 10:10pm UTC

Request Review

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