[TUI] `strata launch` worked then, after a tune had been saved for this PC, every later launch failed
Maintainers usually reply within 3 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- build-system, cli
Research direction
Start with packaging/package_terminal.py and the INSTALLER_TOOLS list, then check the corresponding list in main and how setup.py imports calibrate from tools. Add the missing tool to the bundle and verify that a packaged launch works after a calibration is saved; the setup should finish with the saved settings message and start the model. The other missing files and TUI traceback handling are separate follow-up work.
Written by the indexing model from the issue text.
Description
strata launch worked, then after a tune had been saved for this PC every later launch stopped at Model › "Saving the model's settings" with:
The model could not be installed. Run it again: finished steps are skipped.
Pressing r repeats it. The TUI shows no reason. Running the same setup step by hand shows it:
=== Step 7: writing the start script ===
[ok] KV streaming on: ...
Traceback (most recent call last):
File "...\Strata\terminal\0.1.46.3\setup.py", line 8919, in <module>
sys.exit(main())
File "...\Strata\terminal\0.1.46.3\setup.py", line 8864, in main
import calibrate as CAL
ModuleNotFoundError: No module named 'calibrate'
Cause: the Terminal bundle does not ship tools/calibrate.py. setup.py imports it whenever setup_calibration() finds a saved calibration for this PC and model. Before the first tune nothing is saved and setup passes; once a tune has been saved, every launch fails. packaging/package_terminal.py leaves calibrate out of INSTALLER_TOOLS, and main still does today, so v0.2.2 most likely has the same problem. The Linux bundle uses the same list, so this may be what #3467 is seeing (same message, no reason shown).
Workaround: copy tools/calibrate.py from the commit in the bundle's COMMIT file (here 9de04cd) into <Strata>\terminal\<build>\tools\, then launch again. With that file in place setup ends [ok] the settings tuned for this PC earlier are used and the model starts.
Suggested fix: add "calibrate" to INSTALLER_TOOLS. Two smaller things would also help:
- The launcher only shows a setup error when setup prints a line starting with
[X]. A Python traceback is never shown, so the TUI says only "could not be installed". Showing the last traceback line would have made this a one-minute fix. - A static check of the bundle found other
tools/files thatsetup.pyrefers to but the bundle lacks:image/qimage.py(--images),strata_bench.py(the benchmark question at the end of interactive setup),strata_inspect.py(--inspect) andnvfp4_local_pack.py(NVFP4 models).hip/dll_closure.pyis also missing but setup carries on without it. I did not run into these, so they are unconfirmed, but they would fail the same way.
- Dominant language
- C++
- Stars
- 11.6k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Niko1221/Strata
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Niko1221/Strata#3894 · 2 comments ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Niko1221/Strata#3785 · 2 comments ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 3 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
OpenSpace/OpenSpace#4353 · 1 comment ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
macOS: a double-click on a notarized altairsim is refused, and the docs give only the offline casePossibly taken @anhaoXie claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mutationpp/Mutationpp#337 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bulletphysics/bullet3#4819 ·