Align console behavior with operator routing and image workflow expectations
Constraint: Must preserve current exchange-rate logic, same-group routing boundary, and temporary image-file behavior while fixing UX-visible inconsistencies. Rejected: Large frontend chunk refactor | introduced risky circular chunking and did not improve deliverability for this rollout. Confidence: medium Scope-risk: moderate Directive: Keep channel failover constrained to the selected group and preserve Beijing-day semantics for user cache dashboard metrics. Tested: go test ./controller ./model ./service ./common -count=1; npm run build; remote smoke on source deployment at http://38.76.218.56:18081/ plus /api/status and /api/image-studio/settings. Not-tested: Browser-driven end-to-end verification of every console page interaction.
This commit is contained in:
8
web/src/hooks/dashboard/useDashboardData.js
vendored
8
web/src/hooks/dashboard/useDashboardData.js
vendored
@@ -243,9 +243,11 @@ export const useDashboardData = (userState, userDispatch, statusState) => {
|
||||
}, [userDispatch]);
|
||||
|
||||
const refresh = useCallback(async () => {
|
||||
const data = await loadQuotaData();
|
||||
await loadUptimeData();
|
||||
await loadCacheStats();
|
||||
const [data] = await Promise.all([
|
||||
loadQuotaData(),
|
||||
loadUptimeData(),
|
||||
loadCacheStats(),
|
||||
]);
|
||||
return data;
|
||||
}, [loadQuotaData, loadUptimeData, loadCacheStats]);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user