Loyal-Young opened a new issue, #6466: URL: https://github.com/apache/rocketmq-dashboard/issues/6466
### Describe the bug Attaching to a completed AI run replays a stored terminal `run_status` as `run_finished` with a hard-coded null duration, even when the loaded run row has a recorded `durationMs`. With NON_NULL serialization the field disappears from that replayed SSE frame. The live event contract and the synthetic terminal branch already carry the run duration. ### To Reproduce Complete a run with a recorded duration, then reconnect to its SSE endpoint with a cursor before the persisted terminal event. Inspect the replayed `run_finished` JSON: `durationMs` is absent despite the value on the run row. ### Expected behavior Replay should include the recorded duration when it is available. A run without a duration should retain its existing unknown value rather than inventing one. This is a wire-contract issue; the current UI does not need to read the field to expose it. ### Version and context RocketMQ Studio, branch `rocketmq-studio`, commit `779b8c0`. Previously identified by unbridled-41 in #4999 (issue #5003). That PR was closed by the stale workflow; the hard-coded null remains in `AgentEventProjector.replay`, and no open replacement was found. Regression coverage will inspect the terminal SSE JSON produced by `AiRunService.attach`, including zero and nonzero durations. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
