Closed bug report

0.9.340 shipped archive contains five runtime handler changes absent from master

John Lauer · ·closed by John Lauer

The shipped insiders 0.9.340 archive does not match the latest master source for five runtime handlers, beyond expected version/package metadata.

Verified 2026-09-07: download https://wiki.adom.inc/download/adom/kicad-bridge/0.9.340/adom-bridge-kicad-v0.9.340.zip has SHA256 84c6b60b8cc484c502e2cc78274c9016957f0aeb9f5a34ec82b83b89f7dce68f, exactly the insiders manifest. Current master is 96b31b3ac62c922e0da80ea4a377adfb3cad8ee5 (Publish 1.0.127). Source clone reports complete. Direct repo show at that commit agrees for server.py and BRIDGE_VERSION.

Differing runtime source files: handlers/demo.py (559 diff lines), handlers/open_footprint_editor.py (96), handlers/kicad_ui.py (87), handlers/kicad_windows.py (34), handlers/install_footprint.py (30). Archive has substantial tour/window/library fixes absent from master. Other differences: BRIDGE_VERSION (master 0.9.317, zip 0.9.340), bridge.json, package.json, page.json.

The routing handler in the archive matches master, so routing PR #3 remains based on the right routing code. The concern is reproducibility and loss of shipped tour fixes in a future rebuild from master. Please land the exact tested runtime source and reconcile the version metadata. Attached diff is master to released archive, not a proposal to roll anything back.

Hosts ConfRoomROG, arav-rog, winvm all report runtime 0.9.340 on AB 2.1.68. Runtime tests are ongoing; this report is a source/archive mismatch, not a claim those shipped handlers fail.

release-vs-master.diff

1 Reply

John Lauer ·

Confirmed and fixed at the source. Five handlers (demo.py, install_footprint.py, kicad_ui.py, kicad_windows.py, open_footprint_editor.py) plus BRIDGE_VERSION, bridge.json and page.json never reached master: tools/build_release.py pushed sources in chunks with check=False, and the chunk carrying those files failed silently, release after release since 0.9.318. Master now carries the exact shipped runtime source (commits 95750bc5 to ec6cd73d, 2026-09-07); a fresh clone diffed against the 0.9.340 zip shows no runtime difference. The release tool now checks every push reply and refuses to create the release when any chunk fails, so the repo and the zip cannot drift again. That tool change lands with the next release push.

John Lauer closed this ·

Log in to reply.