Skip to content

fix(dashboard): settle failed refresh requests - #2688

Open
HandSonic wants to merge 1 commit into
OtterMind:mainfrom
HandSonic:fix/dashboard-refresh-settles
Open

fix(dashboard): settle failed refresh requests#2688
HandSonic wants to merge 1 commit into
OtterMind:mainfrom
HandSonic:fix/dashboard-refresh-settles

Conversation

@HandSonic

Copy link
Copy Markdown
Contributor

Summary

  • Ensure dashboard refresh promises settle when requests fail.
  • Prevent the dashboard from remaining in a permanent loading state after an API error.

Validation

  • Focused regression tests
  • Prettier, ESLint, and Stylelint
  • Community web build

Fixes #2682

@HandSonic
HandSonic requested a review from openai0229 as a code owner August 12, 2026 00:57
@openai0229 openai0229 moved this to In Review in Chat2DB Community Aug 12, 2026
@HandSonic
HandSonic force-pushed the fix/dashboard-refresh-settles branch from 3175f5a to aee5e48 Compare August 12, 2026 16:49
@HandSonic
HandSonic force-pushed the fix/dashboard-refresh-settles branch from aee5e48 to e8ac916 Compare August 19, 2026 19:43

@openai0229 openai0229 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking regression: runDashboardRefresh now converts a rejected load into the fulfilled value false, but both callers ignore the boolean. In particular, DingChartModal uses refreshCurrentDashboard().then(() => staticMessage.success(...)), so a failed refresh now displays "pin to dashboard success". Previously that callback did not run on rejection.

Please update callers to distinguish success from failure and use finally for loading cleanup, or preserve rejection while ensuring the refresh button always settles. Add a caller-level test for the failed refresh path, not only the helper test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Review

Development

Successfully merging this pull request may close these issues.

bug(dashboard): failed refresh leaves the button loading forever

2 participants