Repository navigation
v0.12.9 – model catalog merged field by field (router 0.6.9)
Router 0.6.9, agent unchanged (0.16.0). The model catalog is merged field by field.
- What went wrong: an entry in
roles.yaml(written by the UI, usually a measurement) replaced theconfig.yamlentry of the same model entirely. Fields that onlyconfig.yamlset did not apply:max_parallelfor one model (the limit had to be set again through the UI) and a capability override for another. - Now: both entries are merged field by field. Size fields (
weights_gib,kv_gib_per_1k,real, the measured values) still replace each other as a unit, so new weights are never combined with an old measurement. All other fields fromconfig.yaml(max_parallel,capabilities, notes) keep applying unlessroles.yamlsets them. - New selftest
selftest_katalog_merge.pyin CI. - UI: the full-width chart "Models actually used" collapses to its legend line while there were no requests in the last 10 minutes, instead of leaving an empty row; it comes back with the first request.
Deutsch
Router 0.6.9. Katalogeinträge aus config.yaml und roles.yaml werden Feld für Feld zusammengeführt; bisher ersetzte ein Eintrag in roles.yaml den aus config.yaml ganz. Größenangaben bleiben eine Einheit. Das Diagramm „Effektiv genutzte Modelle“ klappt ohne Anfragen in den letzten 10 Minuten auf seine Legendenzeile zusammen.