You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let auto use what is ready, and make naming the engine the thing that builds it
CI found a real one, and it was not about CI: the macOS leg went from 35 seconds
on main to 643 on this branch. Every launch on a Mac without Whisper models was
compiling Swift and then sitting on `--probe` until it timed out, because the
probe waits for an authorization dialog that a headless machine never answers.
A user's first launch would have done exactly the same thing. A full minute of
nothing before a pill appears, on a machine that asked for none of it, to decide
whether to offer an engine it might not use.
So `--engine auto` passes compile_if_missing=False and a ten second probe: it
uses the helper if it is already built and says how to build it if not.
`--engine native` still compiles, because somebody who typed it has asked for
the wait. Once it has been run once, auto finds the binary from then on.
A timeout is now named as the dialog it is rather than as
"probe failed: TimeoutExpired", which is true and useless when the fix is a
click.
And every one of those reasons reaches `say()`, which writes to a cp437 console
- so the em dashes in them were a launch that died on its own explanation. That
is how this one was found; there is a test over the module's string literals now
so the next one is caught here rather than by a user on Windows.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments