davsclaus opened a new pull request, #29477:
URL: https://github.com/apache/camel/pull/29477

   _Claude Code on behalf of davsclaus_
   
   Small things I noticed while walking every tab for #29468 (checked live with 
the circuit breaker example):
   
   - **Beans, Configuration, Heap Histogram, Threads**: the first row is 
selected, so the detail panel shows something, as Errors, Endpoints and Chaos 
already do (`selectsFirstRow`). Before, the detail said "Select a ..." until a 
key was pressed.
   - **Timeline**: paused, the cursor `▲` on the last second was drawn over the 
`now` label of the axis, leaving `n▲▲`; the same at the start and the middle. A 
label the cursor is on is now left out; the time of the cursor is at the right 
of the axis.
   - **JFR**: without an active recording, the tab says how to start one: Java 
Flight Recorder (JFR) checked in the run options (F2 → Open Project...), or 
`jcmd <pid> JFR.start`.
   - **MCP indicator**: with `--mcp` and no agent connected yet, the footer 
showed a red `✗`, which reads as the server failed. It now says `no client` in 
the muted colour (docs updated).
   - **Circuit Breaker**: INFLIGHT is blank when zero, as the other counts of 
the table.
   
   Not changed: Inspect `g` does switch to the waterfall (it replaces the 
Detail panel; I first read only the table).
   
   Tests: `TimelineTabRenderTest` (the axis labels next to the cursor), 
`JfrTabRenderTest` (the hint, and none with a recording), 
`ConfigurationTabRenderTest` (first row selected; two colour tests add a second 
row, as the Errors tests do, since the selection highlight hides the colours of 
the selected row). All 2415 tests of the plugin pass.
   
   🤖 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