pilichoumao opened a new pull request, #6611: URL: https://github.com/apache/rocketmq-dashboard/pull/6611
In demo mode, importing an empty alert-rule document reported success, and a document with 201 rules was appended to the mock inventory. Validate the mock import envelope before constructing or appending any rows: a document, version 1, the requested domain, an array, and 1..200 rules are required. The real backend already enforces the count; this fixes demo behavior only. Real-mode API delegation, accepted 1/200-rule boundaries in both domains, copied rule/channel data and the existing generic upload failure message are preserved. No new UI text, dependencies or backend API changes. Fixes #6610 Validation: - Local service regressions: baseline 7 failures/17 passes; guard passes all 24 service tests. - ECS Node 20: sequential baseline regression run has 9 failures/3 passes (47 unrelated cases skipped); the full service and AlertsPage files pass all 59 cases. After completing the real-API response fixture with its required lastTriggered field, the entire service file was rerun: 24 passed; the page and production source hashes are unchanged. - Invalid envelopes leave both inventories unchanged; real file uploads of 0/201 rules show the existing error and do not refresh a successful import. - Project-reference TypeScript check (tsc -b), formatting and git diff --check passed. Final ECS lint passed (0 errors, 10 existing warnings); production build and license check passed (133 components, 140 license files), and all 5 license-script tests passed. Final source hashes match the pushed files. No production backend bypass, full frontend-suite run, MySQL/Broker integration or Docker image build is claimed. Initial overlapping ECS runs were stopped and excluded; validation evidence comes from the sequential rerun. -- 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]
