dropdown for models seems to reset and not persist #40

Closed
opened 2026-07-20 09:12:38 +00:00 by hugo · 1 comment
Owner

when opening the model dropdown, it is not showing the last list of models. if update models is clicked, then the dropdown shows more models. but the model availability must persist in the database for both the online and offline endpoint and be used for dropdowns and only overwritten when a new model list update is triggered.

when opening the model dropdown, it is not showing the last list of models. if update models is clicked, then the dropdown shows more models. but the model availability must persist in the database for both the online and offline endpoint and be used for dropdowns and only overwritten when a new model list update is triggered.
hugo added the bug label 2026-07-20 09:12:38 +00:00
Author
Owner

Fixed in c80b5d6. Discovered models are now persisted in a new ai_endpoint_models table, keyed per endpoint (online/airplane). The settings and chat model dropdowns hydrate from the persisted list on load, and the list is only replaced when a model refresh for that endpoint succeeds — so it survives tab switches and app restarts. Covered by a unit test for per-endpoint persistence and overwrite-on-refresh; spec updated with an EndpointModelPersistence invariant.

Fixed in c80b5d6. Discovered models are now persisted in a new ai_endpoint_models table, keyed per endpoint (online/airplane). The settings and chat model dropdowns hydrate from the persisted list on load, and the list is only replaced when a model refresh for that endpoint succeeds — so it survives tab switches and app restarts. Covered by a unit test for per-endpoint persistence and overwrite-on-refresh; spec updated with an EndpointModelPersistence invariant.
hugo closed this issue 2026-07-20 10:14:13 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hugo/RuDS#40