fix: skip recovery for already-connected same-net pairs - #1213
Open
GokulPandi-M wants to merge 3 commits into
Open
GokulPandi-M wants to merge 3 commits into
GokulPandi-M wants to merge 3 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
GokulPandi-M
force-pushed
the
fix/redundant-near-parallel-same-net-routes
branch
from
September 16, 2026 16:11
f6f0297 to
c2d0187
Compare
GokulPandi-M
marked this pull request as ready for review
September 17, 2026 01:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reproduction
Reproduction: #1211. Until that PR merges, this branch carries the same captured solver input so the fix PR can show the corrected snapshot from the exact pipeline repro.
Summary
Implementation
Recovery builds the connected component containing the first endpoint from existing same-net traces. Traces join that component when they share a pin or intersect geometrically. If the second endpoint is already in that component, no additional route is generated.
The rule uses only net identity and trace geometry; it has no component names, circuit-specific coordinates, or spacing thresholds.
Validation
bun test— 407 passed, 4 skippedbunx tsc --noEmitbun run format:check