bd: backup 2026-03-05 02:51
This commit is contained in:
parent
18eab6baf2
commit
0b409f68c9
4 changed files with 18 additions and 7 deletions
|
|
@ -1632,3 +1632,11 @@
|
|||
{"actor":"zenchantlive","comment":null,"created_at":"2026-03-04T16:56:55Z","event_type":"created","id":1659,"issue_id":"beadboard-hyc","new_value":"","old_value":""}
|
||||
{"actor":"zenchantlive","comment":"Added label: skill","created_at":"2026-03-04T16:56:55Z","event_type":"label_added","id":1660,"issue_id":"beadboard-hyc","new_value":null,"old_value":null}
|
||||
{"actor":"zenchantlive","comment":"Added label: usability","created_at":"2026-03-04T16:56:55Z","event_type":"label_added","id":1661,"issue_id":"beadboard-hyc","new_value":null,"old_value":null}
|
||||
{"actor":"zenchantlive","comment":null,"created_at":"2026-03-04T18:39:05Z","event_type":"created","id":1662,"issue_id":"beadboard-gsk","new_value":"","old_value":""}
|
||||
{"actor":"zenchantlive","comment":"Added label: gt:agent","created_at":"2026-03-04T18:39:05Z","event_type":"label_added","id":1663,"issue_id":"beadboard-gsk","new_value":null,"old_value":null}
|
||||
{"actor":"zenchantlive","comment":"Added label: role:backend","created_at":"2026-03-04T18:39:05Z","event_type":"label_added","id":1664,"issue_id":"beadboard-gsk","new_value":null,"old_value":null}
|
||||
{"actor":"zenchantlive","comment":null,"created_at":"2026-03-04T18:39:11Z","event_type":"status_changed","id":1665,"issue_id":"beadboard-pdz.1","new_value":"{\"assignee\":\"beadboard-gsk\",\"status\":\"in_progress\"}","old_value":"{\"id\":\"beadboard-pdz.1\",\"title\":\"pdz.1: Investigate why UI queries mail/reservations for all agents\",\"description\":\"TASK CONTEXT\\n- Bead ID: beadboard-pdz.1\\n- Title: Investigate why UI queries mail/reservations for all agents\\n- Parent/Epic: beadboard-pdz\\n\\nTASK CONTRACT\\n- Goal: Find where in the frontend code the mail/reservations API calls are triggered for every agent\\n- Success Criteria:\\n - Identify the component/hook making these calls\\n - Understand why it's called for every agent\\n - Document the call chain\\n- Scope:\\n - Frontend code investigation\\n - Identify the source of the 404 spam\\n- Out of Scope:\\n - Fixing the issue (separate bead)\\n\\nVERIFICATION REQUIREMENTS\\n- Cite exact file paths and line numbers where calls originate\",\"status\":\"open\",\"priority\":0,\"issue_type\":\"task\",\"owner\":\"jordanlive121@gmail.com\",\"created_at\":\"2026-03-04T22:47:01Z\",\"created_by\":\"zenchantlive\",\"updated_at\":\"2026-03-04T22:47:01Z\"}"}
|
||||
{"actor":"zenchantlive","comment":null,"created_at":"2026-03-04T18:42:22Z","event_type":"updated","id":1666,"issue_id":"beadboard-pdz.1","new_value":"{\"notes\":\"INVESTIGATION COMPLETE:\\\\n\\\\nRoot Cause Identified:\\\\n\\\\n1. **Frontend Issue** (social-page.tsx + activity-panel.tsx):\\\\n - social-page.tsx:169-177 derives from ALL visible cards and their agents, then makes separate API calls for EACH agent (lines 187-208)\\\\n - activity-panel.tsx:279-103 builds agent roster from ALL agent-labeled issues (up to 10), then makes parallel calls for EACH (lines 308-325)\\\\n - No batching - each agent gets its own /api/agents/mail and /api/agents/reservations call\\\\n\\\\n2. **Backend Issue** (agent-registry.ts + agent-mail.ts):\\\\n - Both /api/agents/mail and /api/agents/reservations call before processing\\\\n - resolveRegisteredAgent() calls which spawns a subprocess\\\\n - Each subprocess has significant startup overhead (~500-600ms per call)\\\\n - When agent doesn't exist or isn't registered, returns 404 AFTER the expensive subprocess call\\\\n\\\\nCall Chain:\\\\nFrontend:\\\\n- social-page.tsx: (from visibleCards) → refreshCoordination() → Promise.all([agentNames.map(...)]) \\\\n- activity-panel.tsx: (from issues with gt:agent label) → fetchCoordination() → Promise.all([agentRoster.map(...)])\\\\n\\\\nBackend:\\\\n- route.ts GET → inboxAgentMessages() → resolveRegisteredAgent() → showAgent() → callBdAgentShow() → spawn subprocess\\\\n\\\\n**Files to Fix:**\\\\n- beadboard/src/components/social/social-page.tsx (lines 169-219)\\\\n- beadboard/src/components/activity/activity-panel.tsx (lines 279-325) \\\\n- beadboard/src/lib/agent-registry.ts (line 123-138 - subprocess spawning)\\\\n- beadboard/src/lib/agent-mail.ts (lines 192-195, 312-313)\\\\n- beadboard/src/lib/agent-reservations.ts (lines 311-314, 350, 447)\\\\n\\\\n**Recommended Fixes:**\\\\n1. pdz.2: Cache resolved agents in-memory so we don't spawn subprocess for each request\\\\n2. pdz.3: Batch the frontend calls - either fetch all agents' mail/reservations in one call, or only fetch for agents that actually have mail configured\"}","old_value":"{\"id\":\"beadboard-pdz.1\",\"title\":\"pdz.1: Investigate why UI queries mail/reservations for all agents\",\"description\":\"TASK CONTEXT\\n- Bead ID: beadboard-pdz.1\\n- Title: Investigate why UI queries mail/reservations for all agents\\n- Parent/Epic: beadboard-pdz\\n\\nTASK CONTRACT\\n- Goal: Find where in the frontend code the mail/reservations API calls are triggered for every agent\\n- Success Criteria:\\n - Identify the component/hook making these calls\\n - Understand why it's called for every agent\\n - Document the call chain\\n- Scope:\\n - Frontend code investigation\\n - Identify the source of the 404 spam\\n- Out of Scope:\\n - Fixing the issue (separate bead)\\n\\nVERIFICATION REQUIREMENTS\\n- Cite exact file paths and line numbers where calls originate\",\"status\":\"in_progress\",\"priority\":0,\"issue_type\":\"task\",\"assignee\":\"beadboard-gsk\",\"owner\":\"jordanlive121@gmail.com\",\"created_at\":\"2026-03-04T22:47:01Z\",\"created_by\":\"zenchantlive\",\"updated_at\":\"2026-03-05T02:39:11Z\"}"}
|
||||
{"actor":"zenchantlive","comment":null,"created_at":"2026-03-04T18:43:26Z","event_type":"closed","id":1667,"issue_id":"beadboard-pdz.1","new_value":"Investigation complete. Root cause identified: UI makes individual mail/reservations API calls for every agent. Each call triggers resolveRegisteredAgent() → callBdAgentShow() which spawns a bd subprocess (~600ms). For non-existent agents, 404 returned AFTER expensive subprocess call. Fixes: (1) Cache resolved agents in-memory, (2) Batch frontend calls.","old_value":""}
|
||||
{"actor":"zenchantlive","comment":null,"created_at":"2026-03-04T18:47:45Z","event_type":"status_changed","id":1668,"issue_id":"beadboard-pdz.2","new_value":"{\"assignee\":\"beadboard-gsk\",\"status\":\"in_progress\"}","old_value":"{\"id\":\"beadboard-pdz.2\",\"title\":\"pdz.2: Fix slow 404 response times\",\"description\":\"TASK CONTEXT\\n- Bead ID: beadboard-pdz.2\\n- Title: Fix slow 404 response times\\n- Parent/Epic: beadboard-pdz\\n\\nTASK CONTRACT\\n- Goal: Make 404 responses fast (\\u003c50ms instead of ~600ms)\\n- Success Criteria:\\n - /api/agents/mail returns 404 in \\u003c50ms when agent has no mail\\n - /api/agents/reservations returns 404 in \\u003c50ms when agent has no reservations\\n- Scope:\\n - API route optimization\\n - Remove unnecessary delays/lookups in 404 path\\n- Out of Scope:\\n - Changing what 404 means\\n - Mail system functionality\",\"status\":\"open\",\"priority\":0,\"issue_type\":\"task\",\"owner\":\"jordanlive121@gmail.com\",\"created_at\":\"2026-03-04T22:47:16Z\",\"created_by\":\"zenchantlive\",\"updated_at\":\"2026-03-04T22:47:16Z\"}"}
|
||||
{"actor":"zenchantlive","comment":null,"created_at":"2026-03-04T18:51:12Z","event_type":"updated","id":1669,"issue_id":"beadboard-pdz.2","new_value":"{\"notes\":\"IMPLEMENTED:\\\\n\\\\nAdded in-memory cache with 30-second TTL to agent-registry.ts:\\\\n- CacheEntry interface with data + expiresAt\\\\n- agentCache Map for storing resolved agents\\\\n- getCachedAgent() checks cache before spawning subprocess\\\\n- setCachedAgent() stores result with TTL\\\\n- Modified callBdAgentShow() to use cache\\\\n\\\\nThis eliminates repeated bd subprocess spawns for the same agent within 30 seconds. For non-existent agents, the 404 is now cached too so we don't re-validate every request.\\\\n\\\\nVERIFICATION:\\\\n- npm run typecheck: PASS\\\\n- npm run lint: PASS (21 warnings, 0 errors)\\\\n- npm run test: PASS (3/4, unrelated launcher test failure)\"}","old_value":"{\"id\":\"beadboard-pdz.2\",\"title\":\"pdz.2: Fix slow 404 response times\",\"description\":\"TASK CONTEXT\\n- Bead ID: beadboard-pdz.2\\n- Title: Fix slow 404 response times\\n- Parent/Epic: beadboard-pdz\\n\\nTASK CONTRACT\\n- Goal: Make 404 responses fast (\\u003c50ms instead of ~600ms)\\n- Success Criteria:\\n - /api/agents/mail returns 404 in \\u003c50ms when agent has no mail\\n - /api/agents/reservations returns 404 in \\u003c50ms when agent has no reservations\\n- Scope:\\n - API route optimization\\n - Remove unnecessary delays/lookups in 404 path\\n- Out of Scope:\\n - Changing what 404 means\\n - Mail system functionality\",\"status\":\"in_progress\",\"priority\":0,\"issue_type\":\"task\",\"assignee\":\"beadboard-gsk\",\"owner\":\"jordanlive121@gmail.com\",\"created_at\":\"2026-03-04T22:47:16Z\",\"created_by\":\"zenchantlive\",\"updated_at\":\"2026-03-05T02:47:45Z\"}"}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue