The GitHub Actions job "CI" on rocketmq-dashboard.git/codex/async-action-guards has failed. Run started by GitHub user tju-yxq (triggered by tju-yxq).
Head commit for run: 36b0f5665dcc53556737f48d2229c0a6170036ef / Yxq <[email protected]> fix(ai): guard the bare-route conversation creation against a second send The stream-start path already carries a double-submit guard (useAgentRun's "Enter twice in one tick must not admit two runs"), but the bare-route creation path in useAiSend.startRun had none: during the createConversation + default-instance lookup + navigation window the composer stays enabled (no run is in flight yet), and the armed pendingSendRef is a single slot. A second send in that window created a second conversation and silently dropped the first prompt — either the second create overwrote the armed entry (the first question vanished with its input already cleared, leaving an orphaned empty conversation in history) or both fired into two different conversations while the replace-navigation landed on only one. Add the create-phase twin of the stream guard: createInFlightRef is set on entry, held through the armed phase, and released when the route settles on any conversation (or on a failed create). A suppressed send resolves null, which the caller already handles by restoring the prompt into the composer — exactly like a failed create. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38049111056 With regards, GitHub Actions via GitBox
