fix(web): keep app usable on transient instance fetch failure - #9659
fix(web): keep app usable on transient instance fetch failure#9659IsmailofficialGithub wants to merge 1 commit into
Conversation
Only show MaintenanceView if instance data was never loaded, so brief /api/instances/ failures do not force the startup error screen. Fixes makeplane#9658
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthrough
ChangesInstance error handling
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to This localized fix preserves the usable app state after transient instance-fetch failures while retaining the maintenance screen for cold starts without instance data; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description
Only show the maintenance empty state when
/api/instances/fails and instance data was never loaded. Avoid flipping to the startup error screen on brief API restarts or 502s after a successful load.Type of Change
Screenshots and Media (if applicable)
N/A
Test Scenarios
GET /api/instances/failsReferences
Fixes #9658
Summary by CodeRabbit