Frun1na opened a new issue, #4701:
URL: https://github.com/apache/rocketmq-dashboard/issues/4701

   ### Before Creating the Bug Report
   
   - [x] I have searched the [open 
issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository 
and believe that this is not a duplicate.
   
   - [x] This is a defect in RocketMQ Studio, not a usage question and not a 
defect in another Apache RocketMQ repository.
   
   - [x] I can reproduce this on the current `master` branch, or I have stated 
the exact version I am running below.
   
   
   ### Studio Version
   
   branch: rocketmq-studio
   git commit id: 7ce9a68215c4cd1c7025013d02135b43b6aa6ba1
   deployed as: built from source (`cd web && npm ci && npm run build`)
   
   ### Runtime Environment
   
   OS: Windows 11 with WSL2 (Ubuntu 24.04.3 LTS)
   MySQL: 8.0.36, container from `deploy/docker-compose.yml`
   browser: Chrome 141
   
   ### Connected RocketMQ Cluster
   
   Not involved: the defect is in the deliveries page's client-side filter 
loading, reproduced in Vitest with a rejected `listInstances`.
   
   ### Build Toolchain
   
   Node.js 20.19.0, npm 10.8.2
   
   ### Describe the Bug
   
   `web/src/pages/ops/notificationDeliveries.tsx` loads the instance list for 
its instance filter with:
   
   ```js
   useEffect(() => {
     void listInstances()
       .then(setInstances)
       .catch(() => undefined);
   }, []);
   ```
   
   The `catch` discards the failure. The selector renders `instances.map(...)`, 
so the user sees an empty dropdown: no error, no message, and no way to retry 
other than a full page reload. The visible result is indistinguishable from a 
deployment that has no instances registered, which is a different and much less 
likely fact.
   
   Every other load on the page reports its failure 
(`t('deliveries.loadFailed')`), so this is the one silent spot.
   
   ### Steps to Reproduce
   
   1. Open the notification deliveries page while `GET /api/instances` fails 
(stop the backend, or make it return 5xx).
   2. Open the instance filter.
   
   ### What Did You Expect to See
   
   The filter says it could not load its options and offers a retry, rather 
than presenting an empty list as a fact.
   
   ### What Did You See Instead
   
   An empty instance filter with no indication that anything failed.
   
   ### Additional Context
   
   I have a fix ready: PR #4700.
   
   ### Are You Willing to Submit a Pull Request?
   
   - [x] Yes, I am willing to submit a pull request.
   


-- 
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]

Reply via email to