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/02 04:42:17 UTC
[GH] (rocketmq-dashboard/fix/yy-dlq-mock): Workflow run "CI" failed!
The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/yy-dlq-mock has failed.
Run started by GitHub user yyqdbngt (triggered by yyqdbngt).
Head commit for run:
f4003cb9cf4878bfd5f7524447db6e821c6c36e5 / yyqdbngt <bt...@gmail.com>
fix(web): use the backend DLQ status codes in the mock data
web/src/mock/dlq.ts declared status: 'active' | 'empty' and used those
lowercase values in all eight rows, but the only producer,
RocketMQDLQProvider.listDLQGroups
(RocketMQDLQProvider.java:172), emits
statsAvailable ? (messageCount > 0 ? "ACTIVE" : "EMPTY") : "UNAVAILABLE".
The DLQ page renders group.status verbatim and its own fixtures already use
'ACTIVE' / 'UNAVAILABLE', so mock mode was the only place showing a status
the API cannot produce, and a status-driven rendering change could never be
caught against it.
Carry the codes the provider emits in the mock rows and its interface, and
pin the vocabulary, the status/backlog consistency and the %DLQ%{groupName}
topic format with the new web/src/mock/dlq.test.ts.
Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/36965040174
With regards,
GitHub Actions via GitBox