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

   _Claude Code on behalf of davsclaus_
   
   Small bugs and misleading charts found while walking the screens.
   
   - **Process: the arguments after the jar were cut off.** Every token that 
isn't an option was appended to the option before it, so `run README.md 
application.properties circuit-breaker.camel.yaml` joined the `-jar 
…/camel-launcher.jar` line, which was cut off at the edge. `-jar`, `-cp`, 
`-classpath` and `--class-path` now take one value, and each argument after it 
(the main class, the files of `camel run`) gets its own line. Options such as 
`--port 8080` keep their values.
   - **Source: the Info panel described the wrong file.** It always showed the 
file under the cursor of the list, even when the viewer had the focus on 
another file (one opened with `g` or from another tab): `Type: properties` next 
to an open YAML file. When the viewer has the focus, it now describes the open 
file.
   - **Memory: the heap chart title was wrong and the chart had no axis.** The 
title said `(38M / 63M committed)` while 48M was committed: 63M was the top of 
the chart, the most the heap used in its history. The title now says `(38M 
used, 48M committed)`, and the chart has a y-axis with the top, the half and 0.
   - **Timeline: a millisecond of jitter looked like spikes.** The mean-time 
sparkline was scaled to twice the average or the slowest second, so on a route 
of 0 and 1 ms each 1 ms was a full bar. Its height is now at least 10 ms, while 
a slow second still stands out.
   
   Tests: new cases in `ProcessTabRenderTest`, `SourceTabJumpLinksTest`, 
`MemoryTabRenderTest` and `TimelineTabRenderTest`. The full 
`camel-jbang-plugin-tui` suite passes (2420). I checked each one live with the 
`fail-well/circuit-breaker` example.
   
   This merges cleanly with #29468, #29486 and #29493.
   
   🤖 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