davsclaus opened a new pull request, #29507: URL: https://github.com/apache/camel/pull/29507
_Claude Code on behalf of davsclaus_ Two smaller findings from walking the screens. - **Events: `f` shows one category at a time.** A busy route's exchange events (created, sending, sent, completed) fill the table and push the route and context events off it. `f` cycles through all, then each category the events have (`exchange`, `general`, `route`), then all again. The title shows the category (`Events [general]`) and the footer shows `f category [all]`. - **Startup is a waterfall.** The tab drew a bar per step from the left, indented by level, with the name after the bar, so the names were ragged and the bars said nothing about when a step ran. Now each line has the duration, the name indented under its parent, and a bar that starts where the step started and is as long as it took. The steps are in the order they started, and `s` puts the slowest first. The recorder's `beginTime` was already parsed; an older Camel without it keeps the recorded order with the bars from the left. I looked at two other findings and left them out: - The JFR tab could start a recording with `jcmd` itself. But Camel's events in it need the JFR instrumentation, which is only installed when the integration starts with JFR, so a recording started later stays empty. The tab's advice to run with JFR is the right one. - The Inspect diagram's `step 1/7` against the table's 9 steps is by design: it counts the distinct nodes, and the two rows where a route ends revisit a node. The help pages (event.md, startup.md) are updated. Tests: `EventTabOrderTest#fShowsOneCategoryAtATime` and `StartupTabRenderTest#theStepsAreInTheOrderTheyStartedOrTheSlowestFirst`. The full `camel-jbang-plugin-tui` suite passes, apart from `ConfigurationTabRenderTest`, which fails on main and is fixed by #29503. I checked both live with the `fail-well/circuit-breaker` example. 🤖 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]
