zmuxuny opened a new pull request, #7379:
URL: https://github.com/apache/rocketmq-dashboard/pull/7379

   ### Which Issue(s) This PR Fixes
   
   Fixes #7160. Replaces stale-closed #7161 using the refreshed original fork 
branch and preserving authorship.
   
   ### Brief Description
   
   After a successful bulk retry, update both page rows and the selected 
delivery snapshot for succeededIds. A FAILED-filtered reload can remove queued 
rows; the open detail dialog must not then fall back to stale FAILED status, 
attempts, error, and retry controls. Failed IDs are untouched and later server 
rows remain authoritative.
   
   This is the remaining bulk-response boundary after #5665. Open #4384 adds 
filtered cross-page retries; its current source does not fix the existing 
visible-bulk retry snapshot, so this change remains independent. Net diff 
against Studio trunk 7abf8ada is 2 files, +255/-0.
   
   ### How Did You Test This Change?
   
   Rerun November 4 at c9a0b535baa0a457766c87d6e314c3099f2f1ccc:
   - npm test -- 
src/pages/ops/__tests__/NotificationDeliveriesBulkRetry.test.tsx: 6 passed, 
then 6 passed again after the negative control.
   - Same tests against unchanged trunk production code: 2 failed, 4 passed.
   - npx tsc -b --force, changed-file ESLint and Prettier: passed.
   - npm run build: passed, including license check (134 components, 141 
license files).
   
   No full frontend/backend suite or live cluster was run locally. Hosted CI is 
separate; the previous PR had an unrelated Consumer polling test failure, which 
is not presented as a pass here. AI assistance was used for audit and 
validation.
   
   ### Checklist
   - [x] Single coherent fix with regression coverage.
   - [x] Original branch and authorship retained.
   - [x] No new strings, dependencies, backend behavior, or API changes.
   


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