AI_Assistant/pcbjam
Watch
1
0
Fork
You've already forked pcbjam
 0
Code Issues Pull requests Projects Releases 4 Packages Wiki Activity Actions 5
4 releases 4 tags
  • vendor-766e2f4-20260904-r4-debug 014648807f

    vendor-766e2f4-20260904-r4-debug
    Some checks failed
    wasm-build.yml / cmms-embed: VITE_LIBS_SOURCE=static (not off) — install the window.kicadLibs bridge (push) Failing after 0s
    Details
    release / meta (push) Waiting to run
    Details
    release / build (push) Blocked by required conditions
    Details
    release / publish-wasm (push) Blocked by required conditions
    Details
    release / deploy-demo (push) Blocked by required conditions
    Details
    release / deploy-editor (push) Blocked by required conditions
    Details
    release / Build all tools + KiCad e2e (Ubicloud) (push) Waiting to run
    Details
    wasm-build.yml / cmms-embed: VITE_LIBS_SOURCE=static (not off) — install the window.kicadLibs bridge (release) Failing after 0s
    Details
    Pre-release

    AI_Assistant released this 2026-09-04 13:18:07 +10:00 | 0 commits to cmms-embed since this release

    all-DEBUG wasm bundle (4th attempt at the schematic-open abort).

    r1 (release-K/debug-wx, task-#54 mismatch), r2 (--full --release), r3-dist (r2 wasm + static
    libs) ALL abort at the identical spot — right after "[DND] Drag and drop handlers registered",
    during .kicad_sch parse/open. This is ./docker/build.sh kicad_editor -j 4 --full (no
    --release): env.sh defaults DEBUG_BUILD=1, so deps + wxWidgets (--enable-debug) + KiCad
    (-DCMAKE_BUILD_TYPE=Debug -g -O1) + embind (-DDEBUG) are all consistently Debug. Upstream's
    documented default and the config never browser-tested (the very first build was Debug but
    only its --release incremental, r1, got a browser).

    WASM-ONLY (dist stays r3-dist / static libs). kicad_editor.wasm 60,777,740 B (-O1, so a bit
    slower at runtime than r2's -O2 — acceptable for v1). No DWARF sidecar shipped. WebAssembly.compile
    OK (247 imports / 128 exports).

    sha256(pcbjam-vendor-766e2f4-r4-debug.tar.gz) = 835818474b7a2ffd482f6802a4ea152f832228e66beaca55da33a91dc4f483d2

    If this ALSO aborts at the same spot, the next diagnostic step is a --full --diag=coroutine
    build for SuspendError attribution, or filing the merged-kicad_editor + schematic + JSPI path
    upstream.

    Downloads