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

   Fixes to how the camel-jbang monitor starts and watches integrations and 
infra services, one commit each.
   
   **CAMEL-25425: quitting the monitor keeps the files of the examples that 
still run**
   - The examples the monitor starts keep running when it quits, but their 
files were deleted on exit (File.deleteOnExit). A dev-mode example then lost 
its routes.
   - deleteOnExit also cannot delete a folder that is not empty, so hundreds of 
empty `camel-example-*` folders piled up in the temp directory.
   - Now the monitor deletes, on quit, the folders of examples that no longer 
run, plus leftover example folders over an hour old that no running app uses.
   - `camel run --example` deletes its folder recursively, and keeps it with 
`--background`.
   
   **An infra service that fails to start says why**
   - The monitor ran `camel infra run --background`, which loses the output. So 
a service that could not start (Mosquitto cannot bind 1883 while Artemis has 
it) was silent, and the example waiting for it was dropped after 120 s.
   - The monitor now runs `camel infra run` itself, outliving the monitor as 
before, and keeps the output. A failed start shows the failure log at once.
   - An example waits as long as its infra is starting (at most 15 minutes), as 
a first image pull can take minutes.
   
   **The MCP tool that runs an example says whether it started**
   - It answered "started" at once, also for an example that failed seconds 
later.
   - It now waits up to 30 s and answers started, failed (with the end of the 
log, without colors and stack frames), or starting.
   
   **An opened project whose run ended without an app is Stopped at once**
   - It previously showed Starting for up to 5 minutes.
   
   **The monitor shows a failed reload, as `camel ps` does**
   - A dev-mode reload that fails now shows the app as Error on the Overview, 
with the reason in the info panel and a notice.
   - The reason is also given in the Overview table for an agent.
   
   **Tables show their rows again after the list shrinks**
   - The scroll offset is pulled back. Before, after 8 rows became 2, the 
Overview drew only one row and the other app looked stopped.
   
   **camel_control lists infra services for an unknown name**
   - Review follow-up of #27515.
   
   Each fix was verified live: a running example kept its files when the 
monitor quit, the Mosquitto port clash showed its failure log, a missing 
OPENAI_API_KEY was reported as failed in 3 s, and a broken dev-mode route 
showed Error and cleared after the fix.
   
   Tests: new ExampleHelperStaleDirsTest, LaunchManagerInfraTest cases 
(including aws sqs), TableOffsetClampTest, and additions to StatusParserTest, 
LaunchManagerStartFailureTest, OpenedProjectLifecycleTest and 
McpFacadeControlTest. All 1777 tests of the monitor plugin pass.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m


-- 
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