Skip to content

repro: fallback net label leaves orphaned partial V3V3 trace - #1214

Closed
GokulPandi-M wants to merge 1 commit into
tscircuit:mainfrom
GokulPandi-M:repro-esp32-c3-r6-disconnected-trace
Closed

GokulPandi-M wants to merge 1 commit into
tscircuit:mainfrom
GokulPandi-M:repro-esp32-c3-r6-disconnected-trace

Conversation

@GokulPandi-M

@GokulPandi-M GokulPandi-M commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Summary

  • capture the exact SchematicTracePipelineSolver input emitted by mohan-bee/esp32-c3 v1.0.1
  • reduce the snapshot to the MCU section so the R6 failure is visible
  • reproduce the failed R6-to-V3V3 route leaving a partial trace after a fallback V3V3 label is placed

Reproduced behavior

R6 remains logically connected through its fallback V3V3 net label. The failed physical route toward the other V3V3 member is also retained, ending in open space. The incomplete route should be removed when the fallback label is used.

Verification

  • bun test tests/repros/repro-esp32-c3-r6-orphaned-v3v3-trace.test.ts
  • bunx tsc --noEmit

@vercel

vercel Bot commented Sep 17, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
schematic-trace-solver Ready Ready Preview Sep 17, 2026 3:23pm UTC

Request Review

@GokulPandi-M
GokulPandi-M force-pushed the repro-esp32-c3-r6-disconnected-trace branch from 1c64eaa to d18db53 Compare September 17, 2026 15:23
@GokulPandi-M GokulPandi-M changed the title Add ESP32-C3 R6 dangling V3V3 trace repro repro: fallback net label leaves orphaned partial V3V3 trace Sep 17, 2026
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