fightBoxing opened a new pull request, #1405:
URL: https://github.com/apache/flink-agents/pull/1405

   ## Summary
   - Chat retry stops on HTTP 4xx other than 408, 409, and 429. Timeouts, 429, 
5xx, and failures with no HTTP status still use the retry budget.
   - The status is read from the exception or its cause (`statusCode` / 
`getStatusCode` / `code` in Java, `status_code` / `response.status_code` and 
the implicit exception context in Python), so a wrapper does not hide a client 
error.
   - A recorded client error stays non-retryable across recovery. Older durable 
outcomes that omit the flag stay retryable. Watsonx and DashScope now put the 
HTTP status on the exception instead of only in the message.
   
   ## Test plan
   - [x] `mvn -pl plan -am -Dtest=ChatModelInvokerTest test`
   - [x] `mvn -pl integrations/chat-models/watsonx -am 
-Dtest=WatsonxChatModelConnectionTest#testRetryLoop test`
   - [x] `pytest` `test_chat_model_action_retry.py` and 
`test_dashscope_client_error_keeps_http_status`
   
   
   Made with [Cursor](https://cursor.com)


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