runpod: a base and its adapter are two models, not one path (v0.3.39)
Seeds were de-duplicated by `path`. A base model and a LoRA of it share one path
by definition, so the adapter's entry was dropped and the pod was told about the
base alone — observed live, one line after the sibling seeding had correctly
found it:
[runpod] pool 'pool:digesta-qwen38' is shared with: diogene-alpha
[runpod] pod will be told about 1 model(s)
The dedup exists because a capability pod's list can overlap the one model a
per-model pool also seeds, which is a real case; it just has to key on what the
pod will SERVE the entry as — path plus alias, id and adapters — rather than on
the weights the entries happen to have in common.
Orchestrator-side only: the pod registers what it is handed, so no new image.
Co-Authored-By:
Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PxYHWbCAjjjD7A1rhFKtaW
Showing
Please
register
or
sign in
to comment