You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by GitBox <gi...@apache.org> on 2026/10/03 03:44:12 UTC
[GH] (rocketmq-dashboard/fix/ai-attach-admission-window): Workflow run "CI" failed!
The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/ai-attach-admission-window has failed.
Run started by GitHub user unbridled-41 (triggered by unbridled-41).
Head commit for run:
761a68cfb4e1ab170ba1c3569ba5fea790905178 / unbridled-41 <17...@users.noreply.github.com>
fix(ai): attach again when the run leaves the admission window
Reloading the page while a run is still being admitted attaches to a QUEUED
row that has no worker yet. The server cannot register the observer, so it
closes that stream with a bare `done` and no status frame - a clean end for
the client - and the hook marked the run id as attached for the rest of the
visit. Once admission finished and the run started generating, nobody was
watching: no streaming bubble, no error, and the next send was refused with
409 until the operator navigated away and back.
Record the status the attach observed along with the id, so the next timeline
fetch (which reports the same run as RUNNING) attaches once more. A repeated
identical status still returns early, so the anti-hot-loop guarantee the ref
exists for is unchanged.
Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/37093897553
With regards,
GitHub Actions via GitBox