Skip to content

Default legacy Qwen launches to 1.7B - #101

Closed
joshuabrosenthal wants to merge 1 commit into
lukaszliniewicz:mainfrom
joshuabrosenthal:codex/fix-qwen-model-size-persistence
Closed

Default legacy Qwen launches to 1.7B#101
joshuabrosenthal wants to merge 1 commit into
lukaszliniewicz:mainfrom
joshuabrosenthal:codex/fix-qwen-model-size-persistence

Conversation

@joshuabrosenthal

Copy link
Copy Markdown
Contributor

Summary

  • Align the retained installer/launcher fallback for missing Qwen model-size settings with the manager catalogue default of 1.7b.
  • Preserve explicit 0.6b selections and continued support for the official 0.6B Base model.
  • Add regression coverage across installer architecture, launcher behavior, and guided setup.

Root cause

The legacy installer and launcher paths had independent 0.6b fallbacks when kobold_qwen_model_size was absent, while the current manager catalogue defaults to 1.7b. A missing legacy key could therefore silently launch the 0.6B model even when the current UI and manager expected 1.7B.

Impact

Missing legacy model-size values now resolve to 1.7B consistently. Existing explicit 0.6B configurations remain unchanged.

Validation

  • ..\bin\pixi.exe run -e installer-build python -m unittest tests.test_installer_architecture tests.test_installer_launcher_chatterbox tests.test_manager_guided_setup
    • Ran 104 tests ... OK (skipped=1)
  • ..\bin\pixi.exe run -e installer-build python -m py_compile for all 10 changed Python files
  • git diff --check
  • Manual verification that the launcher starts Qwen3-TTS-12Hz-1.7B-Base-f16.gguf and successfully completes a voice-cloning request through the local API.

No user data, credentials, local paths, voice names, or private identifiers are included in the patch.

@joshuabrosenthal
joshuabrosenthal marked this pull request as ready for review August 1, 2026 16:59
@joshuabrosenthal

Copy link
Copy Markdown
Contributor Author

The two Web migration preview jobs fail during test collection because dbus_next is not installed in that workflow environment. The Pandrator Manager test and package workflows pass on Ubuntu and Windows, and the failure appears unrelated to this installer-only change.

@lukaszliniewicz

Copy link
Copy Markdown
Owner

Thank you — this was a real consistency gap. I've incorporated the fix into main for 0.8.0, kept explicit 0.6B selections intact, centralized the implicit 1.7B fallback, and carried over the regression coverage. I also fixed the unrelated missing Manager dependency in the preview workflow. Really appreciate the careful report and validation!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants