lizhimins opened a new pull request, #1403: URL: https://github.com/apache/rocketmq-dashboard/pull/1403
Consolidates twelve related fixes from @Aias00 into a single PR (same approach as #1234 / #1379 / #1381). Each original commit keeps its author, plus one adaptation commit to align with current project conventions. Contents: - #1274 harden message queries, trace validation and resend outcomes (msgId/topic pairing validation, trace failure surfacing, send status check) - #1280 clear stale DLQ state when switching instances - #1282 harden instance-scoped client connection views (instanceId required, producer/connection scoping) - #1288 ignore stale dashboard responses after instance changes - #1293 initialize the H2 schema for development (application-dev sql.init + schema.sql sync with vendor columns and index names) - #1296 reject cloud instances from Remoting admin resolution - #1303 audit cloud credential mutations - #1305 harden and audit managed instance mutations - #1307 audit ACL mutations and clarify local records - #1309 audit K8s certificate mutations and clarify local records - #1311 harden and audit alert rule lifecycle (export only enabled rules) - #1319 validate runtime Topic and Group names Adaptation commit (per project conventions): - audit write failures isolated (try/catch + warn) in Instance/K8sCert/Acl/Alert/CloudCredential services, matching the control-plane audit isolation precedent - Spring StringUtils replaces private isBlank/JDK blank checks in MetadataService and ClientService - Producer page clears stale state in the instance change handler rather than synchronously in an effect (lint rule + antd Select remount stability) Verification: backend 850/850 green; frontend build + 87 files / 449 tests green on the integrated branch. The original PRs will be closed referencing this one once merged. -- 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]
