Repository navigation
fix(anthropic): default client timeout when unset - #2800
Conversation
This comment has been minimized.
This comment has been minimized.
|
The failing CI test was exercising QuarkusRestClientBuilder outside a Quarkus CDI container, unrelated to the timeout fix. I isolated the regression test around the timeout defaulting logic and pushed 686b27c; this keeps the test deterministic and independent of REST client bootstrapping. |
This comment has been minimized.
This comment has been minimized.
686b27c to
fe4ef62
Compare
This comment has been minimized.
This comment has been minimized.
|
Can you please build with Java 25 and ensure the changed docs are committed? Thanks |
QuarkusAnthropicClient dereferenced builder.timeout unconditionally, so programmatically built Anthropic models threw a NullPointerException when no timeout was configured. Apply the same 15-second fallback that DefaultAnthropicClient uses, before configuring the Quarkus REST client. Fixes: quarkiverse#2798
fe4ef62 to
1e664e9
Compare
|
Rebased onto current The branch is now a single commit on top of The MCP Conformance failure on the previous head looks unrelated: its log ends at |
Status for workflow
|
QuarkusAnthropicClientdereferencedbuilder.timeoutunconditionally, so programmatically built Anthropic models failed with aNullPointerExceptionwhen no timeout was configured. The LangChain4j Anthropic client contract defines a 15-second default when no timeout is provided; this change applies the same fallback before configuring the Quarkus REST client.A focused runtime test verifies that the client builder can be constructed without an explicit timeout.
Local Maven verification is currently blocked because the configured internal repository resets while resolving the parent artifact
io.quarkiverse:quarkiverse-parent:21.QuarkusAnthropicClientNPEs when the builder sets no.timeout(…)#2798.