Skip to content

fix(server): resolve unload-by-alias 400s#135

Merged
marksverdhei merged 1 commit into
htfrom
fix/122-unload-alias
Jun 20, 2026
Merged

fix(server): resolve unload-by-alias 400s#135
marksverdhei merged 1 commit into
htfrom
fix/122-unload-alias

Conversation

@marksverdhei

Copy link
Copy Markdown

Fixes #122

Maintains a robust `alias_to_name` map in `server_models` to resolve aliases even if they are shadowed or lost on the loaded instance's meta object. This fixes issue #122 where direct-to-node unload by alias returned 400 even while the model was hot.
@marksverdhei
marksverdhei force-pushed the fix/122-unload-alias branch from 456c9d0 to 8ea0f36 Compare June 18, 2026 11:08
@marksverdhei
marksverdhei merged commit 6ee3bb7 into ht Jun 20, 2026
9 checks passed
@marksverdhei
marksverdhei deleted the fix/122-unload-alias branch June 20, 2026 11:08
marksverdhei added a commit that referenced this pull request Jun 21, 2026
Maintains a robust `alias_to_name` map in `server_models` to resolve aliases even if they are shadowed or lost on the loaded instance's meta object. This fixes issue #122 where direct-to-node unload by alias returned 400 even while the model was hot.

Co-authored-by: marksverdhei <mark.sverdhei@gmail.com>
marksverdhei added a commit that referenced this pull request Jun 27, 2026
Maintains a robust `alias_to_name` map in `server_models` to resolve aliases even if they are shadowed or lost on the loaded instance's meta object. This fixes issue #122 where direct-to-node unload by alias returned 400 even while the model was hot.

Co-authored-by: marksverdhei <mark.sverdhei@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Router: unload-by-alias 400s when models-dir catalog scan shadows a preset alias

1 participant