Fehler in der LLM-Nutzungsoberfläche

zogstrip · 6. Januar 2026 um 11:05

Guter Hinweis, @RBoy – ich habe auch vergessen, den Cache zu verwalten/leeren, wenn die Periode geändert wird

github.com/discourse/discourse

FIX: Update model/feature dropdowns when changing time period in AI usage

main ← fix/ai-usage-dropdown-cache

opened 11:04AM - 06 Jan 26 UTC

ZogStriP

+91 -90

Follow-up to a1cc09d22d. The model and feature dropdown lists in the AI Usage… admin page weren't updating when users changed the time period. For example, switching from "Last month" to "Last 24 hours" would still show models that had no usage in the last 24 hours. The root cause was a race condition in the caching mechanism. The cache was being cleared inside the async `fetchData` method, but tracked property changes in methods like `setPeriodDates` would trigger Glimmer re-renders before the cache was cleared. This caused the stale cached values to be used during re-render. Additionally, the cache could be populated with empty arrays during initial render before the AJAX response arrived, preventing proper population once data was available. The fix moves cache invalidation to happen synchronously before any tracked property changes, and only populates the cache when actual data is present. This ensures the dropdown options always reflect the currently selected time period. Ref - https://meta.discourse.org/t/bug-in-llm-usage-ui/392652

Thema		Antworten	Aufrufe
Minor UI bug in LLM Usage page UX pr-welcome , ai	2	51	16. Dezember 2025
Discourse AI admin usage page - custom date range issues Bug ai , fixed	2	78	17. September 2025
Usage not showing LLM models Bug ai	3	53	30. November 2025
AI helper model site setting is hidden now but still in use Bug ai	5	109	2. September 2025
Vague LLM warnings on dashboard Support ai	2	48	7. November 2025

Fehler in der LLM-Nutzungsoberfläche

Verwandte Themen