davsclaus opened a new pull request, #27219:
URL: https://github.com/apache/camel/pull/27219
_Claude Code on behalf of davsclaus_
Bugs found while walking through the TUI with the examples and the Spring
Boot/Quarkus examples.
- **Error bodies shown escaped.** Camel JSON-escapes the body of a message
dump, so a JSON body showed as `{\"orderId\":...}` in the Errors tab, its
diagram and `camel_get_errors` (the AI saw it that way too). The Inspect tab
already unescaped it at display time. The body is now unescaped once when
parsed (Errors, History, Browse), and in `camel_get_errors`.
- **Inspect said `elapsed:0ms`** for a 17 ms exchange. It took the first
step flagged as last, which is the return of a route called over direct. It now
takes the last one.
- **0 msg/s for a Quarkus or Spring Boot app in prod.** These apps don't run
the load statistics, so they report no throughput while their total grows. The
TUI now measures the rate from the totals of the last 10 s of polls
(`RateEstimator`). A rate the app reports is still used.
- **A Spring Boot app that fails to start stayed "Starting".** A launch was
watched for 8 s only. It is now watched until Camel says it started, the
process ends, or its output shows `APPLICATION FAILED TO START`, `[ERROR] BUILD
FAILURE` or `Failed to start application`. Then the process is stopped and the
Failed panel shows the log. The JVM staying up is fixed separately in
CAMEL-25230.
- **`tui_navigate` could not find an opened project by its folder name**
once it ran under its app's own name (`camel.main.name`).
Tests: `StatusParserTest`, `HistoryTabRenderTest`, `RateEstimatorTest`,
`LaunchManagerStartFailureTest`, `McpFacadeFindIntegrationTest`,
`AuthoringToolsTest`. The module tests 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]
