Slicing: the Bambu Studio version check has no time limit, so a held launch hangs the turn #210

Activity

1. pullfrog commented on Nov 8, 2026

   

   pullfrogBot

   on Nov 8, 2026 – with Pullfrog

   Last edited by pullfrog

   More actions

   detect_version currently collapses every probe failure into None, so a timeout must be propagated explicitly rather than reported as an unknown or unvalidated version. Discovery probes all candidates, and Settings uses the same path.

   Implementation plan

   1. Replace the unbounded --help wait with a bounded probe (for example, 15 seconds). On timeout, terminate and reap the child; handle captured output without allowing full pipes or inherited descriptors to defeat the deadline. Preserve the private scratch directory and relative executable support.
   2. Carry a distinct timeout error through chosen paths, environment overrides, discovery, slicing, and Settings. In discovery, retain the ability to select a later validated candidate; if none succeeds, surface the timeout with actionable guidance, including the macOS prompt possibility.
   3. Add fast deterministic tests using a short injected deadline and a hanging fake executable. Assert bounded completion, process cleanup, and the surfaced error for slicing/discovery and Settings; retain successful version parsing and scratch isolation coverage.

   Related: #39 established the probe's scratch directory requirement; #208 concerns a separate readiness check that misreports a timeout.

     ^{｜ Implement a fix ➔ ｜ View workflow run ｜ via Pullfrog ｜ Using gpt-6.1-terra ｜ 𝕏}
2. pullfrog

   added

   bugSomething isn't workingSomething isn't working

   rustPull requests that update rust codePull requests that update rust code

   on Nov 8, 2026