flm v0.9.43 invalidates some already pulled models
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 152
- Avg merge
- 4h 14m
- Merged PRs (30d)
- 11
Description
I've upgraded flm from 0.9.42 to the last version because installation of lemonade complained that it wasn't ok but latest flm did not liked a model that previously worked fine.
$ flm list
...
[FLM] Local model gemma4-it:e4b version: 0.9.40 < 0.9.43
[FLM] Model gemma4-it:e4b is not compatible with the current FLM version.
- gemma4-it:e4b ⏬
...
B.T.W. I've uninstalled lemonade (as I prefer using bleeding edge straight compiled llama.cpp and comfyui) and downgraded flm to the previous version in order to regaining access to the previously working model
Contributor guide
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.
Research direction
Reproduce the report with FLM 0.9.42 and 0.9.43 using the existing gemma4-it:e4b model, starting with the flm list output shown in the issue. Trace the model-version compatibility check and determine why the previously usable model is marked incompatible; done means an upgraded FLM either accepts that model or reports a justified migration requirement without unexpectedly invalidating it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100