KiCad - the KiCad Bridge
Public Made by Adomby adom
Drive your own KiCad from an AI, in the background: open every editor, read the whole board as data (the EDA Bridge Standard board model), stack-up, part heights, netlists, place, route, pour, DRC and exports.
Background demo job hangs in footprint3d when no Footprint Editor window exists (job slot then blocked)
Background demo job can hang forever in the footprint3d beat
Seen live on AdomLapper 2026-08-24 while verifying the new demo captions (0.9.248): the background job ran beats 1-5, then sat in footprint3d for 10+ minutes (progress frozen, active: true), which also blocks any future demo run because the job slot is single-occupancy. The same build completed 6/6 on ConfRoomROG minutes earlier.
Suspected shape: the box had DUPLICATE demo window sets (an accidental staged call had opened one set before the background job opened its own), and at hang time no window titled "Footprint Editor" existed at all, while two "3D Viewer" windows did. handle_open_3d_viewer {editor:"footprint"} appears to wait unboundedly for a footprint-editor context in that state.
Fixes to make:
- Time-budget the beat handlers the same way #54 budgeted show_symbol - a beat that cannot finish returns a failed beat, never wedges the job thread.
- The demo job should carry a hard wall-clock ceiling (sum of estimates x3) after which it marks itself done with the failed beats listed.
- open_3d_viewer {editor:"footprint"} should fail fast with a real errorCode when no Footprint Editor window exists, instead of waiting.
Cleared on the box by a bridge respawn. Captions themselves verified working (6/6 on CRR; caption pixels on-screen on AdomLapper).