You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
Schaerer Damien
authored and
Schaerer Damien
committed
fix(engine, code): a model nobody could start, a window silently ignored, and six editor defects
THE ENTRY THAT COULD NOT START ON ANY MAC. A registry model whose only
measurement is a 92 GB cache, taken on a far larger machine, made eco ask
for more than perf: the mode names mean smallest and largest footprint,
and unclamped eco returned that 92 GB while perf returned the ceiling. The
step-down from perf therefore walked toward a HEAVIER footprint and never
converged, so every mode was impossible. The card was shown as
installable, min_ram_gb was satisfied, a speed was printed, and the user
found out after downloading 202 GB and building a 190 GB pack.
Both measured branches are clamped now, like the no-curve branch already
was. The test states it as the invariant rather than as a number: if perf
can start, eco must be able to start. Verified by removing the fix, where
it reports perf planning 14 GB while eco demands 100.
THE CONTEXT WINDOW SETTING WAS COSMETIC ON TWELVE MODELS. ctx_per_slot_for
clamps the request to what the model declares, and no MoE entry declared
anything, so all of them fell to a cautious 32K ceiling while the button
stayed lit on whatever had been chosen: picking 128K left 128K on screen
over an engine serving 32K. Nine entries now carry the window from their
own published config (Qwen3-Coder and Qwen3-Next at 256K, gpt-oss and
GLM-4.5-Air at 128K, OLMoE at 4K), and the engine reports the window it is
actually serving so the panel can say when a request was capped. The three
whose configuration is not public keep the cautious ceiling, which is what
they had.
SIX IN THE EDITOR.
The change gutter never updated while typing: the marks were computed once
at open and frozen, so twenty lines in, the bar still described the file as
it had been. The debounce and the cache were already there for it.
Creating, renaming or deleting from the tree left the file index stale for
the whole session: a new file was not offered by the palette and a renamed
one kept answering under its old path in project search.
The outline recomputed on every pause in typing whether or not anyone was
looking at it, forcing a syntax tree with a 50 ms budget on the main
thread for a panel that was not on screen.
And in a split, the linter ran the other pane's document under the focused
pane's filename: a .rs on the right was diagnosed as if it were the .md on
the left, so its sources went silent or returned another file's positions.
The linter now reads the path from the state it is given, which is exactly
what the docRel facet exists for.
en: "Family, size on disk, and how many of its experts run per token: a Mixture-of-Experts model uses a few of them at a time, which is why it can be larger than your memory.",
764
764
fr: "Famille, taille sur le disque, et combien de ses experts tournent par jeton : un modèle Mixture-of-Experts n'en utilise que quelques-uns à la fois, et c'est pour cela qu'il peut dépasser votre mémoire.",
765
765
},
766
+
"settings.ctxCapped": {
767
+
en: "Running at %s tokens: this model was not trained for more.",
768
+
fr: "En cours à %s jetons : ce modèle n'a pas été entraîné pour plus.",
769
+
},
766
770
"news.title": {en: "What changed in %s",fr: "Ce qui a changé dans la %s"},
0 commit comments