btlqql opened a new pull request, #5835: URL: https://github.com/apache/rocketmq-dashboard/pull/5835
## Why `applyProxyHome` re-checks the request id after the health-probe (topology) call resolves, but the failure path falls straight through to `setProxyNodes` / `persistProxyAddress` without that check. When a newer load supersedes an older one and the older probe then rejects, the superseded request writes its stale base node list back over the newer result. ## What changed - Re-check the request id on the topology-failure path in `applyProxyHome` and bail out when superseded, mirroring the success path. ## Validation - New test `ProxyStaleTopology.test.tsx`: first load parks on a pending probe, a refresh completes with different nodes, then the old probe rejects — the refreshed list must stay. Fails before the fix, passes after. - Existing `Proxy.test.tsx` suite (16 tests) still passes: `npx vitest run src/pages/studio/__tests__/Proxy` -- 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]
