Repository navigation
Conversation
…r, the rows say their integration, and get about is a list The pid was text in the JSON of trace, browse and logger; the rows of get error, get history and top source had no pid or name; get about --json was an object for one integration and a list for more; and --sort=age of get route and get route-group sorted the youngest first, the opposite of the listings of the integrations. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
🔄 Backport BotThis bugfix targets
Add a Backport PRs will be created automatically on merge (once a port label is added). Comment ℹ️ If you push additional commits after |
|
🧪 CI tested the following changed modules:
🔬 Scalpel shadow comparison — Scalpel: 5 of 726 tested, 8 compile-only — current: 5 all testedMaveniverse Scalpel detected 5 affected modules (current approach: 5). Skip-tests mode would test 5 modules (2 direct + 5 downstream), skip tests for 8 (generated code, meta-modules) Modules Scalpel would test (5)
Modules with tests skipped (8)
💡 Manual integration tests recommended:
All tested modules (15 modules, 2m 17s total)Total reactor time: 2m 17s
Top 20 slowest modules:
|
Item 5 of CAMEL-26929 (JSON and output), the parts about the shape of the JSON. The ANSI codes in piped output are in #29924 (no ANSI codes when stdout is not a terminal).
Problems and changes
pidwas text in the JSON ofcamel cmd trace(status),camel cmd browseandcamel cmd logger, and a number elsewhere. It is a number, withJsonValues.pidas in the other listings (now public, for the action commands). The JSON of these three commands is new in 4.24, so no released output changes.camel cmd stubhad a number already.camel get error --json,camel get history --jsonandcamel top source --jsondid not say which integration they are of. They start withpidandnamenow, as the other listings; the rest of the row is as before.camel get about --jsonwas an object for one integration and a list for more. It is a list, also for one. Its JSON is new in 4.24.--sort=ageofcamel get routeandcamel get route-groupsorted the youngest first, the opposite of the listings of the integrations: those sort by when the integration started, and the uptime of a route is how long it runs. The routes now sort the oldest first too. The Javadoc ofRowSort.integrationsaid "how long the integration runs" while its callers pass the start time, and now says so.The JSON section of the exit codes page (
camel-jbang-exit-codes.adoc) says that a list is a list also for one integration, and that a row of a listing haspid(a number) andname.Not in this PR:
uptimestays a duration in the JSON ofget routeandget route-group(it is so since 4.23, and the TUI reads it), and "nameis the file name in the action commands and the short name in the listings" needs its own look;cmd sendand the trace dump have no--jsonyet.Tests
ListErrorTest.testJsonOutput,CamelHistoryActionTest.testJsonOutputIsTheRecordedHistory,CamelSourceTopTest.jsonHasTheNumbersAndTheCode: the rows have thepidand thename.CamelTraceActionTest.statusAsJson: thepidis a number.ListAboutTest.asJson: a list of one.CamelRouteStatusTest.sortByAgeIsTheOldestFirst(new): a route that runs for 2 hours comes before one that runs for 5 seconds.ExportTestfailed once and passed on the rerun, as on other branches).Claude Code on behalf of davsclaus
🤖 Generated with Claude Code