davsclaus opened a new pull request, #29623: URL: https://github.com/apache/camel/pull/29623
Two small findings from the let there be chaos dialog (CAMEL-26760). **Times out is never marked tried.** The advisor suggests "Times out" for an HTTP call (an `error` rule with `after=` and a `SocketTimeoutException`) as kind `slow`. Once it ran, `ChaosAdvisor.kindOf` counted it as `errors`, so the suggestion never showed as tried. On an HTTP route, trying the 503 rule would also have marked it tried. An error that waits first is now kind `slow`, a timeout, as the suggestions have it. The kinds in chaos.adoc say so, and the catalog copy is updated. **The dialog (L on the Chaos screen) remembers the budget and the picks.** When it closes (Esc or Enter), the budget and the picked rules are kept per integration while the TUI runs. The next time it opens, it has that budget and those picks, so you can change the routes and try the same rules again. If none of those rules is suggested any more, the dialog picks its own as before. Tests: - `ChaosTriedTest#theKindOfARule`: a timeout is kind `slow`. - `ChaosExploreTest#theDialogOpensWithTheBudgetAndThePicksOfLastTime` - `ChaosExploreTest#thePicksOfLastTimeThatAreNoLongerSuggestedAreNot` All tests of camel-chaos (857) and the TUI plugin (2509) pass. _Claude Code on behalf of Claus Ibsen_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_012nJsFsjqqFiwroeHRWaKbS -- 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]
