app
Fusion - the Fusion 360 Bridge
Public Made by Adomby adom
Drive Autodesk Fusion 360 from the cloud via Adom Bridge: component libraries, IPC package generation, board layout, exports (STEP/Gerbers/BOM/CPL), fast APS cloud search, and parametric modeling.
← Commit history
Update 74 file(s)
9 files changed
+71−19
BRIDGE_VERSION+1−1@@ -1 +1 @@-1.9.241+1.9.242
adom-bridge-fusion-manifest.json+4−4@@ -1,10 +1,10 @@ { "manifest_version": 1, "name": "fusion360",- "version": "1.9.241",- "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.241/adom-bridge-fusion-v1.9.241.zip",- "sha256": "621a31601afae9206e64f09cddd6aeabaded0903125f0e68376ce461c994cb0e",- "size": 539350,+ "version": "1.9.242",+ "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.242/adom-bridge-fusion-v1.9.242.zip",+ "sha256": "5d5eef701317852fde605ead1b5f1b061eb928588cff439e53d2764824b6bba7",+ "size": 540242, "verbPrefixes": [ "fusion_" ],
bridge.json+1−1@@ -2,7 +2,7 @@ "manifest_version": 1, "name": "fusion360", "displayName": "Autodesk Fusion 360",- "version": "1.9.241",+ "version": "1.9.242", "description": "Drive Autodesk Fusion 360 from the cloud: launch Fusion, electronics board layout, design rules, exports (STEP/IGES/STL/3MF/USDZ/OBJ/DXF/DWG/Gerbers/BOM/CPL), fast APS server-indexed cloud search plus browse/recent/file-info/versions, cloud file download/upload and folder creation, and in-app parametric modeling (fusion_run_modeling_script). Never-charge: APS calls are capped to the free tier.", "homepage": "https://wiki.adom.inc/adom/fusion-bridge", "author": "Adom Inc.",
dashboard/Cargo.lock+1−1@@ -4,7 +4,7 @@ version = 4 [[package]] name = "fusion-dashboard"-version = "1.9.241"+version = "1.9.242" dependencies = [ "serde_json", ]
dashboard/Cargo.toml+1−1@@ -1,6 +1,6 @@ [package] name = "fusion-dashboard"-version = "1.9.241"+version = "1.9.242" edition = "2021" [dependencies]
install.sh+1−1@@ -21,7 +21,7 @@ echo "Installed fusion-bridge skills: $(ls "$PKG_DIR/skills" 2>/dev/null | tr '\ # binary (the three-artifact pattern: bridge zip -> ab, THIS pkg -> container skills + # this download, page media -> wiki). Per the wiki's PKG_VS_RELEASE policy, binaries are # platform-tagged RELEASE assets, never tarball content - the installer fetches them.-DASH_VERSION="1.9.241"+DASH_VERSION="1.9.242" DASH_URL="https://wiki.adom.inc/download/adom/fusion-bridge/${DASH_VERSION}/fusion-dashboard" DEST="" if [ -w /usr/local/bin ]; then DEST=/usr/local/bin
package.json+1−1@@ -1,6 +1,6 @@ { "slug": "fusion-bridge",- "version": "1.9.241",+ "version": "1.9.242", "type": "app", "description": "This package installs the bridge's SKILLS into your container so your AI knows how to drive it; Adom Bridge loads the bridge runtime itself from the release zip.", "dependencies": {
page.json+11−8@@ -1,6 +1,6 @@ { "slug": "fusion-bridge",- "version": "1.9.241",+ "version": "1.9.242", "type": "app", "description": "This package installs the bridge's SKILLS into your container so your AI knows how to drive it; Adom Bridge loads the bridge runtime itself from the release zip.", "dependencies": {@@ -11,6 +11,10 @@ "uninstall": "./uninstall.sh" }, "tags": [+ "ab",+ "bridge",+ "fusion",+ "desktop-app", "fusion360", "autodesk", "cad",@@ -75,7 +79,10 @@ "build a basic parts library", "add a 3d model to a component", "make a fusion 360 library with 3d",- "set up the fusion bridge"+ "set up the fusion bridge",+ "fusion dashboard",+ "fusion status page",+ "open the fusion launch page" ], "discovery_pitch": "Use the Adom Bridge Fusion 360 bridge when the user wants to DRIVE Autodesk Fusion 360 from the cloud: open/search their team's Fusion cloud designs, lay out a PCB or do electronics, export STEP/IGES/STL/Gerbers/BOM, or build a component library with real rendering 3D. It runs Fusion on the user's own machine via Adom Bridge. NOT for web/browser/login/form-filling (that's the native-browser extension) and NOT for KiCad (that's the kicad bridge).", "brief": "Drive Autodesk Fusion 360 from the cloud via Adom Bridge: component libraries, IPC package generation, board layout, exports (STEP/Gerbers/BOM/CPL), fast APS cloud search, and parametric modeling.",@@ -104,9 +111,5 @@ "label": "Part volume", "prompt": "How much material does each printed part in this assembly use?" }- ],- "author": {- "name": "John Lauer",- "email": "[email protected]"- }-}+ ]+}
server.py+50−1@@ -4217,6 +4217,49 @@ def _build_in_flight(): # captures forever - a stuck marker must not become a permanent refusal. return {k: v for k, v in _BUILD_IN_FLIGHT.items() if now - v < 3600} +def _reconcile_orphaned_runs():+ """At bridge start, fail every run the PREVIOUS bridge process left mid-flight.++ 2026-08-28: run a34157c45412 sat at "proving DAC80504 (1 of 1), 95%, 0 frames" for+ twenty minutes with the add-in idle and no dialog on screen - because three+ bridge_installs had respawned the bridge while it ran. A chain is a daemon thread of+ the bridge process; a respawn kills it, but the run's persisted state keeps saying+ "proving" forever. The wiki then rendered a live progress bar over a corpse, and the+ single-flight guard attached the next press to the corpse. A respawn is the ONLY way+ a chain thread vanishes, so bridge start is the one reliable place to notice: any run+ persisted as in-progress here has no thread and must be marked failed, honestly.+ """+ import tempfile as _tf, json as _js, time as _t+ try:+ _p = os.path.join(_tf.gettempdir(), "fusion-prove-runs.json")+ if not os.path.exists(_p):+ return 0+ runs = _js.loads(open(_p, encoding="utf-8").read()) or {}+ orphaned = 0+ for rid, st in runs.items():+ if st.get("stage") not in ("done", "failed", None):+ st.update(stage="failed", success=False, verdict="not_proven",+ errorCode="bridge_restarted_mid_run",+ error=("The bridge process restarted (a bridge_install or crash) while "+ "this run was at '%s', which killed the run. Nothing after that "+ "stage happened. Start the import again." % st.get("stage")),+ orphanedAt=_t.time())+ orphaned += 1+ if orphaned:+ open(_p, "w", encoding="utf-8").write(_js.dumps(runs))+ try:+ _PROVE_LAST[0] = dict(list(runs.values())[-1])+ open(os.path.join(_tf.gettempdir(), "fusion-prove-last.json"), "w",+ encoding="utf-8").write(_js.dumps(_PROVE_LAST[0]))+ except Exception:+ pass+ _bridge_action_ledger("bridge_started", {"orphanedRunsFailed": orphaned})+ return orphaned+ except Exception as e:+ print("[Fusion Bridge] orphan reconcile failed: %s" % e)+ return 0++ def _publish_run_state(run_id: str, state: dict): """Write a run's state to the SAME per-run store fusion_prove_result already reads. @@ -13256,6 +13299,9 @@ def main(): # while Fusion is up (locked add-in files simply skip via the per-target OSError # catch); the update lands on the next bridge respawn with Fusion closed # (fusion_stop -> bridge_install -> fusion_start).+ _n = _reconcile_orphaned_runs()+ if _n:+ print(f"[Fusion Bridge] {_n} run(s) were mid-flight when the previous bridge died - marked failed (bridge_restarted_mid_run)") print(f"[Fusion Bridge] Syncing AdomBridge add-in (idempotent; updates a stale copy)...") try: install_addin()@@ -13559,7 +13605,10 @@ def _handle_live_feed(fusion_info: dict, args: dict) -> dict: _LIVE_FEED["thread"] = _th.Thread(target=_run, daemon=True); _LIVE_FEED["thread"].start() return {"success": True, "started": True, "channel": channel, "intervalSec": interval, "maxSec": max_sec,- "_hint": "Frames land in shotlog channel %r tagged [main #n] (the 1 fps video) and "+ "_hint": "⚠️ KNOWN LIMIT (2026-08-28): this runs on the Windows bridge, which has no "+ "adom-shotlog and no container paths, so frames do NOT reach shotlog from here "+ "yet - drive the capture loop from the container until the ring-buffer redesign "+ "lands. Intended contract: frames land in shotlog channel %r tagged [main #n] (the 1 fps video) and " "[popup #n.m] (dialogs/panels over it, tied to their tick). Proof frames " "from the import chain are a third kind and carry their own step labels. " "Open with: adom-shotlog open -c %s --skinny. Stop with action:stop." % (channel, channel)}