spuru9 opened a new pull request, #29761:
URL: https://github.com/apache/flink/pull/29761

   ## What is the purpose of the change
   
   The Netty Shuffle Buffers table on the TaskManager Metrics page has shown 
empty Available and Total cells since 2.0. The page still reads REST fields 
that FLINK-36355 removed.
   
   ## Brief change log
   
   - Read `nettyShuffleMemorySegmentsAvailable` / 
`nettyShuffleMemorySegmentsTotal` in `task-manager-metrics.component.html` 
instead of the removed `memorySegmentsAvailable` / `memorySegmentsTotal`.
   - Declare both fields on the `Metrics` interface in 
`interfaces/task-manager.ts`.
   - Switch the spec mock to the current field names and add a test for the 
rendered counts.
   
   ## Verifying this change
   
   - New spec test `shows the Netty shuffle buffer counts` fails without the 
template change and passes with it. `npm run lint`, `npm run test:ci` and `npm 
run build` pass.
   - Checked against a local standalone cluster: `GET /taskmanagers/<id>` 
returns 4096/4096. Before the fix both cells are blank; after the fix both show 
4,096.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Opus 5.5
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


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