Frun1na opened a new issue, #4819: URL: https://github.com/apache/rocketmq-dashboard/issues/4819
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) and found no similar issue. ### What Happened On the Ops configuration page, an operator who selects a NameServer from the list (not yet saved) loses that selection by switching the display language in the top bar: the select silently snaps back to the stored current NameServer. The page's load effect depends on `fetchFailedMessage`, a string derived from `t('ops.fetchFailed')`, so a language change re-runs it — and the re-run ends with an unconditional `setSelectedNamesrv(data.currentNamesrv)`. This is the same root cause #4590 fixed for the instance selection in `BrokerCluster.tsx`; `Ops.tsx` still had the unguarded setter. ### Expected Behavior An unsaved selection that still appears in the freshly loaded NameServer list should survive the language change; only a selection that no longer exists falls back to the stored current NameServer. -- 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]
