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

   [CAMEL-26817](https://issues.apache.org/jira/browse/CAMEL-26817): every 
suggestion of what to try (`camel cmd chaos-suggest`, `ChaosManager.suggest()`, 
key `w` in the TUI) now says what should hold despite its faults.
   
   Before, only the hand-off suggestion (`orders->shipping:lost<=0`) and a 
duplicate with a receiving route had an expectation. An experiment of an 
exploration needs one, so the other suggestions could not be run as an 
experiment as they were, and a rule added from one passed whatever happened.
   
   - A suggestion without an expectation gets `expect=<route>:failed<=0`: every 
exchange its faults hit in the route is recovered by redelivery or handled by 
the error handler, and none just fails.
   - A route without error handling for the fault then fails the verdict, which 
is the finding. A route with a dead letter channel, redelivery or a circuit 
breaker with a fallback passes.
   - For two faults at once, the expectation is on the first rule; messages the 
dead letter channel did not take fail the verdict as before.
   - The hand-off and duplicate suggestions keep their own expectation.
   
   This is step 1 of the start dialog of an exploration in the Camel TUI (let 
there be chaos, CAMEL-26760): pick suggested rules, and run one experiment each.
   
   Tests: `ChaosAdvisorTest.everySuggestionSaysWhatShouldHold`, and the tests 
that check the suggested rules (advisor, dead letter, pairs, stubs) expect the 
expectation. All camel-chaos tests (846) and the chaos tests of 
camel-cli-connector pass. Docs: What to try in `chaos.adoc` (and its catalog 
copy), and `camel-jbang-managing.adoc`.
   
   _Claude Code on behalf of davsclaus_
   
   🤖 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]

Reply via email to