fix(engine): warn when the served model id defaults to a generic dir name #49
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/served-model-name-default"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Following the README's docker examples mounted the checkpoint at /model,
so ServedModelName silently defaulted to the meaningless id "model" and
every request naming the real model got a baffling 404. Warn at startup
when the defaulted id lands on a generic basename, log the served id in
the "gllm serving" line so the operator can see it, and pass
--served-model-name in the README's docker examples.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
Automated review by pr-reviewer v0.37.0 | Safety Check | Claude Sonnet 5 | tracking id
r-60a87e-ebdd7bThis is an AI-generated review and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — Small, low-risk logging/warning addition with no security or breaking-change concerns.
The change is small, low-risk, and does what it says: adds a warning log when ServedModelName defaults to a generic basename, logs the served model id in the startup line, and updates README examples to pass --served-model-name explicitly. No secrets, no destructive logic, no breaking API changes. The eng.ModelID() call assumes such a method exists and returns the resolved name post-setDefaults, which seems reasonable given the diff context. No tests added, but this is a minor logging/warning feature, not core logic, so low risk.
e3ab3f3e5dc44ec503c2Automated review by pr-reviewer v0.37.0 | Safety Check | Mistral Small | tracking id
r-60e3bb-d70526This is an AI-generated reveiw and may contain mistakes.
Status: ✅ Completed
✅ Verdict: LGTM — No issues found
The changes are focused, address the described issue, and introduce no obvious bugs, security issues, or accidentally committed files. The warning for generic model names and updated README instructions are appropriate.