The GitHub Actions job "CI" on rocketmq-dashboard.git/codex/trace-topic-trim-v2 has failed. Run started by GitHub user tju-yxq (triggered by tju-yxq).
Head commit for run: 959cde80930898866a00517331e468bf9271413b / Yxq <[email protected]> fix(message): trim the custom trace topic in the manual trace query The manual trace query (按 Message Key / 按 Message ID 的查询轨迹按钮) passed the custom trace topic to the API raw, while every other path for the same field trims it: the row-opened trace load normalizes before both the cache key and the request, the persistence layer stores the trimmed value (typing " CUSTOM_TRACE " persists "CUSTOM_TRACE"), and history replay restores it trimmed. A whitespace-padded topic — the exact thing that happens when the value is pasted from a ticket — made the manual query look up the padded topic name and fail or return nothing, while the identical input worked through the row's 轨迹 button. Trim the field in runTraceQuery, mirroring loadMessageTrace. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38055995576 With regards, GitHub Actions via GitBox
