A profile may load weights of its own
The catalog had one source a model, so an embedding model served by vLLM from its repository on a card and by llama.cpp from a GGUF on CPUs had its entry swapped by hand halfway through the metallurgy import. A profile's source is what its engine loads and placement looks for; the model's is the default, and what updates and canaries move. ctl model add checks every source, the GGUF check reads each llama.cpp profile's, and ctl weights collects none a profile loads. An empty source leaves a profile's fingerprint as it was, so running replicas do not read as stale. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
497e4b24a1
commit
63198f2753
12 files changed
+218
-35
No files matched your search
@@ -30,7 +30,7 @@ type OrphanView struct {
|
||||
func (a *API) Orphans() []OrphanView {
|
||||
var wanted []string
|
||||
for _, m := range a.ctl.Catalog().Models() {
|
||||
wanted = append(wanted, m.Source)
|
||||
wanted = append(wanted, m.WeightSources()...)
|
||||
// A model's adapters are its weights too; collecting them would
|
||||
// leave replicas that cannot restart.
|
||||
for _, ad := range m.Adapters {
|
||||
|
||||
Reference in new issue
Block a user