goutamadwant opened a new pull request, #12398:
URL: https://github.com/apache/seatunnel/pull/12398

   ### Purpose of this pull request
   
   Related to #11665. Add the UI follow-up to the worker resource endpoint 
introduced in #11909.
   
   The Workers page currently displays four monitoring fields without using the 
resource snapshot. This change adds resource columns and a details drawer using 
existing endpoints.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes.
   
   - Display CPU, heap, physical memory, GC, threads, slots, tags and 
running-job counts.
   - Distinguish fixed-slot capacity from dynamic-slot usage.
   - Refresh automatically without overlapping requests.
   - Clear failed snapshots and distinguish unavailable values from zero.
   - Support IPv6, mixed-role members and partial endpoint responses.
   - Keep the Master page monitoring-only.
   
   No backend API, configuration, dependency or scheduling changes. Response 
collection time is not heartbeat freshness. Historical metrics and task-level 
drill-down remain outside this PR.
   
   ### How was this patch tested?
   
   - All 52 frontend unit tests passed.
   - Three Cypress fixture tests passed.
   - Separate Chromium smoke covered resource rendering, IPv6, escaped tags, 
unavailable responses and master routing.
   - Production build, TypeScript checks and changed-file lint passed.
   - Scoped formatting/verification and repository-wide verification with tests 
skipped passed.
   
   Browser tests use REST-contract fixtures, not a deployed cluster.
   
   ### Check list
   
   - [x] English and Chinese documentation updated.
   - [x] Unit and browser coverage added.
   - [x] No new dependencies or binary packages.
   - [x] No incompatible API or configuration changes.
   - [x] Connector registration changes are not applicable.


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