Repository navigation
Partner v0.1.3
Partner v0.1.3
A fix release for the two things v0.1.2 got wrong around installing and updating. Its installer wrote the two engine server scripts as files named engines\tts and engines\kws-asr, which is where the engine folders have to go: downloading the engines failed on a fresh install, and installing over an install that already had them failed too. This build writes the scripts inside their folders, clears the old placeholder from both sides (an installer hook and the engine download itself), and hands the new installer /UPDATE /P so an update installs over the previous version and leaves the downloaded engines where they are. The MCP handshake also got its own timeout, because a slow-starting server was being read as a broken one.
Fixes
The installer wrote the engine scripts as files, so downloading and updating both failed
bundle.resources in map form treats the value as the full target path, not a directory. "../engines/tts/tts-server.py": "engines/tts/" therefore installed a file called engines/tts holding the script (byte-identical, 15,453 bytes) — exactly where the engine folder belongs.
- Downloading the engines failed. Extraction creates
<root>/tts, the path was a file, so the multi-gigabyte transfer died at the unzip with "a file already exists". - Installing over an install that had engines failed. The installer wanted to write a file where the download had left a folder, and NSIS could not. The maintenance page's default ("uninstall before installing") did not help.
The resource targets now name the file, and nsis/hooks.nsh deletes the stray file before the copy — only when it is a file, never a directory: engines\tts\*.* matches only a directory, and that directory is the downloaded engine. EnginePackage clears the same leftover before extracting, so a person still on the v0.1.2 installer gets the engines from Download instead of an error.
An update installs over the previous version
- The installer is started with
/UPDATE /P: it installs over the recorded directory instead of running the old uninstaller, and needs no answers on the maintenance and directory pages. engines/is not in the installer's manifest, so the runtimes and models already downloaded are left alone — nothing to download a second time.- The API sidecar is stopped first, because the installer overwrites
api/*and Windows will not replace a running image.
The MCP handshake has its own timeout
- "Longest wait" used to bound the
initializehandshake as well as tool calls, covering two different things: the server answering, and the child process starting. A colddotnettakes 300–400 ms to boot, which a short per-call timeout cannot absorb, and on a loaded machine the handshake lost that race — the server read as broken rather than slow. - The handshake is now bounded by the server's own
startTimeoutSeconds(default 30 seconds); every other request keeps the per-call timeout. - The settings hint says so: this value does not affect start-up.
Upgrading
- Install v0.1.3 directly. The placeholder v0.1.2 left behind is cleared by the installer, or by the engine download when that comes first; either way the layout repairs itself.
- From v0.1.3 on, an in-app update no longer uninstalls first. The v0.1.2 shell does not know the new switch, so updating from it still shows the installer's maintenance page. The uninstaller only removes engine folders that are empty, so the runtimes already downloaded stay — it is the last time that page has to be clicked through.
- The engines are still not in the installer: download them from Settings → Local engines; the URLs and SHA-256 are pinned to the
engines-v1release.
Engineering
- A Rust test asserts the hand-off runs the installer in update mode (
/UPDATE,/P), so the switches are a value a test reads rather than a string inside a spawn call. - An API test covers a tree in the old layout: the stray file is removed and extraction creates the folder.
- The desktop "look again" test asserted an elapsed time against the default delay, which measures the OS timer rather than the loop. It now waits an explicit 200 ms and asserts half of that, so timer skew cannot close the margin while a loop that stopped waiting still fails.
The voice engines are downloaded from the engines-v1 release on first use; their URLs and SHA-256 are pinned in this build. The app code is MIT licensed; the engine runtimes and model weights keep their own licences, see THIRD-PARTY-NOTICES.md in the release assets.