shibo - @Rishabh

this is preventing tscircuit package from updating

I know, you need to update the core with the latest version of `kicad-to-circuit-json`

<@452450065941004289> was working on a PR for that

https://github.com/tscircuit/core/pull/2450

tests are failing the tests are flaky because they assert exact rendered images for large imported trace networks whose element ordering is not guaranteed to be stable across runs. iremoved the snapshot checks

Can you explain more with an example? They should be ordered

Why it's happening after updaing the package version?

repro116: Before the dependency update: - imported Arduino Uno data had roughly: - 188 pcb_trace - 188 source_trace - so there was effectively a 1:1 mapping - order was simpler and the rendered result was more stable After updating kicad-to-circuit-json / kicadts: - the same board imports as: - 188 pcb_trace - 109 source_trace - now multiple pcb_trace rows can share the same source_trace_id

Even that shouldn't be dropping traces in the snapshot. We still have the same number of pcb_trace before and after so the snapshot should be same

<@1079361271687807026> Is this related to the trace split mapping to the trace id change you did?

we are not doing trace splitting for normal traces, its only related to breakout points and also did not find any issues in core while i was doing it and the change was only related to breakouts. And we are not creating 2 traces for normal components. I dont think its a breakout srj issue

Traces are same number right so whys it dropping traces?

maybe it's an old issue

v0.0.72 is a trace related fix maybe

The package update did not reduce the number of physical PCB traces. The Arduino Uno import still produces 188 pcb_trace records. What changed is the grouping: the import now yields fewer source_trace records, so one source_trace_id can map to multiple pcb_traces.

core was still written for the old 1:1 assumption and only inflated one trace per source_trace_id, which made some routed segments disappear in the inflated output. So the drop was happening during core inflation, not in kicad-to-circuit-json import.

Can you check if it's a source_trace_id assignment issue in core?

Is it a core issue?

yes ig

was able to update till v0.0.71 without any issue

https://github.com/tscircuit/core/pull/2460

v0.0.72 causes trace loss

What changed in 0.0.72? Ws it related to traces

trace mapping issue in core ig

i think <@778624824875941908> can explain this better https://github.com/tscircuit/kicad-to-circuit-json/pull/105

Ig guess core correctly assigns the source_trace_ids, otherwise there would have been issues in other repos as well. I think it's a kicad-to-circuit-json issue

@here fix without modifying the tests: https://github.com/tscircuit/core/pull/2461

i was close 😅

it's blocking me so we gotta get this issue resolved asap

<@809856037376491570> how's it looking?

no issue

`The Spice Must Flow`

<@809856037376491570> did the refactor