← Commit history

1.9.141: warm-start persistence gate (no Fusion exits between library imports)

John Lauer ·53eb3cc762 ·1mo ago ·parent f3141c6
6 files changed +50−16
BRIDGE_VERSION+1−1
@@ -1 +1 @@-1.9.140\ No newline at end of file+1.9.141\ No newline at end of file
adom-bridge-fusion-manifest.json+4−4
@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "fusion360",-  "version": "1.9.140",-  "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.140/adom-bridge-fusion-v1.9.140.zip",-  "sha256": "2ec401b93b2bdaa7b101b97143cb4c39c5b63bda586cfb45d2bdf7d3b8bea735",-  "size": 475140,+  "version": "1.9.141",+  "url": "https://wiki.adom.inc/download/adom/fusion-bridge/1.9.141/adom-bridge-fusion-v1.9.141.zip",+  "sha256": "a82f18ed2897830c3aea07a698002ee4170f2dff41b1e1605c0df1dd9a711fe9",+  "size": 475671,   "verbPrefixes": [     "fusion_"   ],
bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "fusion360",   "displayName": "Autodesk Fusion 360",-  "version": "1.9.140",+  "version": "1.9.141",   "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.",
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.9.160",+  "version": "1.9.161",   "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+10−7
@@ -1,6 +1,6 @@ {   "slug": "fusion-bridge",-  "version": "1.9.160",+  "version": "1.9.161",   "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",@@ -70,7 +74,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.",@@ -99,9 +106,5 @@       "label": "Part volume",       "prompt": "How much material does each printed part in this assembly use?"     }-  ],-  "author": {-    "name": "John Lauer",-    "email": "[email protected]"-  }+  ] }\ No newline at end of file
server.py+33−2
@@ -711,8 +711,39 @@ def _handle_launch(fusion_info: dict, args: dict) -> dict:                           "this machine; only past roughly 2x p90 is a restart justified."),             }         if not addin_ok:-            print("[Fusion Bridge] warm start found NO add-in and it is NOT busy - restarting "-                  "Fusion so the add-in loads (issue #39, guarded by the busy check from #41)")+            # ⛔ PERSISTENCE GATE (John, 2026-08-22, live during the ab library-matrix run):+            # "you better not be exiting fusion between library imports." A single missed 5s+            # probe between back-to-back imports is NOT "the add-in never loaded" - Fusion's+            # main thread can be digesting the previous import (the command already returned,+            # so /status shows busy:false) and answer again seconds later. Killing on one+            # missed probe exits Fusion mid-matrix. Re-probe over ~30s; kill ONLY if the+            # add-in stays dead the WHOLE window and never reports busy.+            for _re in range(3):+                _t0.sleep(8)+                if wait_for_addin(timeout=5):+                    addin_ok = True+                    break+                try:+                    _st2 = _check_addin_status(timeout=3.0)+                except Exception:+                    _st2 = None+                if _st2 and _st2.get("busy"):+                    return {+                        "success": False,+                        "error": "Fusion is running and the add-in reported BUSY during the "+                                 "persistence re-probe - NOT restarting it.",+                        "errorCode": "fusion_addin_busy",+                        "busyCommand": _st2.get("busyCommand"),+                        "elapsedSeconds": _st2.get("elapsedSeconds"),+                        "alreadyRunning": True,+                        "startKind": "warm",+                        "_hint": ("Do NOT call fusion_start again - poll fusion_readiness and "+                                  "wait; a busy add-in answers again when its command finishes."),+                    }+        if not addin_ok:+            print("[Fusion Bridge] warm start found NO add-in after a ~30s persistence window "+                  "(never busy, never answered) - restarting Fusion so the add-in loads "+                  "(issue #39, #41 busy guard, + the 2026-08-22 library-matrix persistence gate)")             try:                 handle_fusion_kill(fusion_info, {})   # a non-serving add-in will not close politely                 _t0.sleep(3)                          # brief settle; the launch below is what matters