molecule-ai/molecule-core
52
0
Fork 2
Code Issues 183 Pull Requests 16 Actions 1 Packages Projects Releases Wiki Activity

chat: agent reply intermittently never renders in My Chat (persisted but only present as hidden node) — E2E Chat run-to-run divergence on IDENTICAL trees #2598

New Issue
Open
opened 2026-06-11 18:01:40 +00:00 by core-devops · 0 comments
core-devops commented 2026-06-11 18:01:40 +00:00
Member
Copy Link
Copy Source

Evidence (no-flakes rule — this is a real race, not an env issue): E2E Chat on PR #2597 head 9076eaad = GREEN; on merge commit ad24de9 (IDENTICAL tree — merge-queue FF of the same head onto 035123b) = RED (run 349272). Same code, divergent outcome ⇒ timing-dependent product behavior.

Failure shape (tests 2,3,4,6,7; test 1 'panel loads' passes — the #2597 selector scoping works):

Locator:  getByText('Echo: Persistence test')
Expected: visible / Received: hidden
  19 × locator resolved to <p>Echo: Persistence test</p>  ← element EXISTS, hidden

The user message IS visible in My Chat; the echo reply was persisted (its text exists in a hidden DOM node — activity/preview pane), but My Chat never renders it within 15s. This is the same class the CTO reported live ("I leave chat, come back, only see 3 dots") that #2560 partially addressed: when the WS delivery race loses (socket subscription established after the reply lands / missed onAgentMessage), My Chat shows nothing until a manual reload-triggered refetch.

Asks:

  1. Make My Chat reply rendering race-free: reconcile from chat-history (DB) on a short interval or on WS (re)connect, so a missed socket frame can't permanently hide a persisted reply.
  2. Keep the E2E assertion as-is — it correctly demands the reply become visible; do NOT scope it to tolerate the hidden copy.
  3. Regression test at the unit level: simulate socket-subscribe-after-reply ordering.

Context: 4 prior mechanical layers in this suite were fixed via #2576/#2577/#2587/#2597 (sqlmock args, hidden-concierge wsName selector, duplicate #tab-chat ids, duplicate chat-panel testid). This 5th layer is behavioral and owned by the chat stack (#2560/#2530 family).

🤖 Generated with Claude Code

**Evidence (no-flakes rule — this is a real race, not an env issue):** E2E Chat on PR #2597 head `9076eaad` = GREEN; on merge commit `ad24de9` (IDENTICAL tree — merge-queue FF of the same head onto 035123b) = RED (run 349272). Same code, divergent outcome ⇒ timing-dependent product behavior. Failure shape (tests 2,3,4,6,7; test 1 'panel loads' passes — the #2597 selector scoping works): ``` Locator: getByText('Echo: Persistence test') Expected: visible / Received: hidden 19 × locator resolved to <p>Echo: Persistence test</p> ← element EXISTS, hidden ``` The user message IS visible in My Chat; the echo reply was persisted (its text exists in a hidden DOM node — activity/preview pane), but **My Chat never renders it** within 15s. This is the same class the CTO reported live ("I leave chat, come back, only see 3 dots") that #2560 partially addressed: when the WS delivery race loses (socket subscription established after the reply lands / missed onAgentMessage), My Chat shows nothing until a manual reload-triggered refetch. **Asks:** 1. Make My Chat reply rendering race-free: reconcile from chat-history (DB) on a short interval or on WS (re)connect, so a missed socket frame can't permanently hide a persisted reply. 2. Keep the E2E assertion as-is — it correctly demands the reply become visible; do NOT scope it to tolerate the hidden copy. 3. Regression test at the unit level: simulate socket-subscribe-after-reply ordering. Context: 4 prior mechanical layers in this suite were fixed via #2576/#2577/#2587/#2597 (sqlmock args, hidden-concierge wsName selector, duplicate #tab-chat ids, duplicate chat-panel testid). This 5th layer is behavioral and owned by the chat stack (#2560/#2530 family). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
approved
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 do-not-merge
hold from auto-merge (design review in progress)
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 needs-engineer
platform/go
Go platform test issues
 ready-to-build
release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 hongming-personal infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2598
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?