pilichoumao opened a new pull request, #6903: URL: https://github.com/apache/rocketmq-dashboard/pull/6903
Fixes #6897 Metrics query history previously used one browser key for every account. Version and scope keys by stable user ID (username fallback), keep anonymous deployments separate, and remount the explorer on account changes to discard old history, credentials and pending replays. Query completion/persistence must still match the initiating scope and request generation. Existing clear-history and ordering guards remain intact. **Draft pending maintainer agreement on compatibility choices in #6897:** the old unowned key remains untouched but is not read or automatically migrated; auth-disabled/mock deployments retain a separate new anonymous history. This is local browser history isolation, not a claim of server authorization bypass or credential disclosure. Verified locally: 95/95 tests across the page, history utility, authStore and authStorage; full frontend ESLint (0 errors, 10 warnings); changed-file formatting. Tests cover account visibility/clearing/restoration, stable ID and username fallback, anonymous mode, unowned legacy data, blocked storage and late profile/custom results after an account change. The ECS research prototype previously reproduced the leak. Formal implementation ECS mutation checks, grouped regression runs and production build/license checks are pending while the first PR's ECS frontend comparison finishes. This draft starts standard CI; its verification section will be updated with actual results. Independent base: rocketmq-studio a92c23144408cdf5729707050e9ecd9b75f1bad0; does not include #6901 or #6883. No dependencies, backend schema, auth API or generated files changed. Page tests use the real auth store with mocked query APIs; no live dual-account server/browser acceptance run is claimed. -- 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]
