The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/trace-subbefore-retry-count has failed. Run started by GitHub user zjncs (triggered by zjncs).
Head commit for run: e47964f75ca49c7b44c2e0407ec24bc2965c6058 / zjncs <[email protected]> fix(trace): join SubBefore retryTimes into the consumer delivery status The consumer status built from SubAfter trace contexts hardcoded retryCount(0). A message's retry count lives only in the SubBefore context (RocketMQ 5.5.0 TraceDataEncoder: type, timeStamp, regionId, groupName, requestId, msgId, retryTimes), which the parser dropped entirely — so retried deliveries were never flagged and the frontend retry diagnostics (retryCount > 0 severity/issues) could never fire. Collect the SubBefore retry count keyed by requestId — the encoder stamps the same requestId on both ends of one consume attempt — and join it into the SubAfter-built consumer status. The map lives at the query level because an attempt's SubBefore and SubAfter can be flushed into different trace messages; trace messages are processed in store order, so the before-context precedes its after-context. Also add the missing @Test annotation on the pre-existing batched Pub/SubAfter parse test, which was silently skipped. Signed-off-by: zjncs <[email protected]> Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/37189104218 With regards, GitHub Actions via GitBox
