The GitHub Actions job "CI" on 
rocketmq-dashboard.git/fix/api-test-fixture-contract has failed.
Run started by GitHub user Frun1na (triggered by Frun1na).

Head commit for run:
e17f376aa528c128f7d482bd68da2004ab23b4fd / Frun1na 
<[email protected]>
test(web): align API test fixtures with the backend contract

Several api-layer test fixtures and mock datasets carried values the
server never sends, the same pattern that let the consumer page render
raw filter-mode codes for weeks behind a green suite:

- liteTopic: session status 'active' and ttlStatus 'active' — the backend
  emits ACTIVE / EXPIRED for session status and UNKNOWN / EXPIRED /
  EXPIRING_SOON / ACTIVE for TTL status (all compared case-sensitively by
  the LiteTopic page filter).
- dlq: group status 'active' — the provider emits ACTIVE / EMPTY /
  UNAVAILABLE. mock/dlq.ts used the same stale pair and now matches the
  real union, so mock mode mirrors the API.
- producer: client language 'JAVA' — ProducerConnectionService serializes
  ClientLanguage.name(), which is 'Java'.
- message trace: deliveryStatus 'SUCCESS' — the DeliveryStatus enum is
  lowercase success / failed / pending.
- system alerts: level 'critical' — AlertLevel is error / warning / info
  (the page-level test that deliberately feeds an unknown level keeps
  doing so; the api passthrough test now uses a real value).
- mock/consumers: subscription filterMode used the pre-#4732 display
  strings ('Tag 过滤' / 'SQL92 过滤' / '全量'); the API returns TAG /
  SQL / CLASS_FILTER, so mock mode now renders like a real server, and
  the subscriptionDataType union gains TopicType.LITE.

No production code changed; the fixtures now exercise the values the API
actually returns.

Report URL: 
https://github.com/apache/rocketmq-dashboard/actions/runs/36883490341

With regards,
GitHub Actions via GitBox

Reply via email to