Skip to content

qwen3.6-windows-server v1.3.9, portable Windows launcher

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 May 15:23
· 3 commits to main since this release
v1.3.9
8dfb436

qwen3.6-windows-server v1.3.9

Bugfix release: a follow-up to the v1.3.8 fix for the LOADING-stuck
dashboard. v1.3.8 added a 60-second grace before the runtime-manifest
GC could fire, but a second deletion path in the manifest reader
bypassed that grace and silently unlinked the file on any read error.
Issue #12 reporter on Russian Windows 11 still hit it.

What changed

  • launcher/app/runtime.py: _read_manifests no longer unlinks a
    manifest when the read fails. Read errors (Windows file-sharing race
    against the snapshot's os.replace write, partial JSON read,
    transient OSError) are skipped and retried on the next 2-second
    poll. Snapshots clean up their own manifest on exit, and the
    launcher's Unload path clears it via clear_manifest_for_port. The
    reader has no business deleting a file it failed to read this poll.
  • Diagnostic log file at logs\launcher.diag.log. The Textual TUI
    takes over the terminal so print() from the runtime poll is
    invisible in scrollback. Diagnostics now append to a file:
    manifest-read failures land here with the exception type, and the
    post-grace GC line lands here too. If the dashboard sticks again, a
    single type logs\launcher.diag.log reproduces the full poll
    history.

Who is affected

  • Anyone who hit the LOADING-stuck dashboard on v1.3.8 despite the
    60-second grace. The new path is hardened against the read-error
    unlink and the diagnostic log makes future debugging a one-line
    paste.

Upgrading

update.bat

The launcher zip is replaced; venv\, models\, logs\,
cuda13_shim\ and user_config.json are preserved. The bundled wheel
is unchanged from v1.3.7, so the runtime install is not rerun.

Verification

After upgrading, launch any snapshot from the TUI and let it sit
through the full vLLM compile / autotune window. The card should
progress LOADING -> RUNNING and logs\runtime\<port>.json should
remain on disk for the whole session. If the card sticks on LOADING
again, paste the contents of logs\launcher.diag.log in the issue.

Files

  • qwen3.6-windows-server-portable-x64-ampere.zip
  • qwen3.6-windows-server-portable-x64-blackwell.zip
  • SHA256SUMS.txt
Assets 5
Loading