mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

⚠️ [Feature] Fix async response handling in dashboard (Issue #92) #298

New Issue
Closed
opened 2026-02-03 22:30:42 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-02-03 22:30:42 +00:00
Owner
Copy Link

Summary

Dashboard uses setTimeout hack to wait for query responses.

Location

apps/web/src/app/(authenticated)/federation/dashboard/page.tsx:57-62

Issues

  • Race conditions possible
  • Unreliable data loading
  • Poor UX with arbitrary delays

Required Implementation

Choose one approach:

  1. WebSocket notifications - Subscribe to response events
  2. Polling mechanism - Poll message status
  3. Request/response correlation - Callback URLs

Acceptance Criteria

  • No setTimeout hacks
  • Reliable query response delivery
  • Loading states properly managed
  • Error handling for failed queries
  • Real-time updates

Priority

HIGH - Poor UX and race conditions

Related Issues

Completes work started in Issue #92

## Summary Dashboard uses `setTimeout` hack to wait for query responses. ## Location `apps/web/src/app/(authenticated)/federation/dashboard/page.tsx:57-62` ## Issues - Race conditions possible - Unreliable data loading - Poor UX with arbitrary delays ## Required Implementation Choose one approach: 1. WebSocket notifications - Subscribe to response events 2. Polling mechanism - Poll message status 3. Request/response correlation - Callback URLs ## Acceptance Criteria - [ ] No setTimeout hacks - [ ] Reliable query response delivery - [ ] Loading states properly managed - [ ] Error handling for failed queries - [ ] Real-time updates ## Priority **HIGH** - Poor UX and race conditions ## Related Issues Completes work started in Issue #92
jason.woltje added the webp1 labels 2026-02-03 22:30:42 +00:00
jason.woltje added this to the M7.1-Remediation (0.0.8) milestone 2026-02-03 22:31:35 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label p1 web
Milestone
No items
No Milestone M7.1-Remediation (0.0.8)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#298
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?