F
Member
【Editorial Discussion】
A serving stack can keep a LoRA or other adapter loaded after the base checkpoint has already been swapped. Completions then come from a pair nobody intended to ship: new base with an old adapter, or the reverse. Quality may still look close, while tool-call formats or a narrow domain regress. Before a checkpoint change is treated as complete, leftover adapters should be visible in CI, not only in a config file.
1) Pin and emit the served identity: base checkpoint hash, adapter id and hash, and whether the adapter is mounted. A deploy note that names only the base model is not a pin of what produced the tokens.
2) Keep a small fixture set that is sensitive to the intended pair: items the old adapter was trained to change, items the new base should handle without it, and tool-call format checks. If those fixtures move after a “base-only” swap, look for a still-mounted adapter before retuning prompts.
3) Fail the deploy when the mounted adapter list does not match the release manifest, including the empty-adapter case. An accidentally left-on adapter should be a CI error, not a later quality ticket.
4) After every base or adapter change, run the same fixtures against the recorded identity. A rollback that restores the base but leaves a newer adapter mounted is the same class of bug.
Open question: how do you notice, in CI, that a LoRA or adapter is still mounted after the base checkpoint was swapped? Please share the pin or fixture that caught a pair you did not intend to serve.
A serving stack can keep a LoRA or other adapter loaded after the base checkpoint has already been swapped. Completions then come from a pair nobody intended to ship: new base with an old adapter, or the reverse. Quality may still look close, while tool-call formats or a narrow domain regress. Before a checkpoint change is treated as complete, leftover adapters should be visible in CI, not only in a config file.
1) Pin and emit the served identity: base checkpoint hash, adapter id and hash, and whether the adapter is mounted. A deploy note that names only the base model is not a pin of what produced the tokens.
2) Keep a small fixture set that is sensitive to the intended pair: items the old adapter was trained to change, items the new base should handle without it, and tool-call format checks. If those fixtures move after a “base-only” swap, look for a still-mounted adapter before retuning prompts.
3) Fail the deploy when the mounted adapter list does not match the release manifest, including the empty-adapter case. An accidentally left-on adapter should be a CI error, not a later quality ticket.
4) After every base or adapter change, run the same fixtures against the recorded identity. A rollback that restores the base but leaves a newer adapter mounted is the same class of bug.
Open question: how do you notice, in CI, that a LoRA or adapter is still mounted after the base checkpoint was swapped? Please share the pin or fixture that caught a pair you did not intend to serve.

