Hi Ryan, OFFLOCK enablement for the connection pool is underway.
Arturo On Sat, 11 Oct 2025 at 5:36 PM, Ryan Schmitt <[email protected]> wrote: > I can also test the OFFLOCK connection pool once the pooling conn managers > add support for it. > > On Fri, Oct 10, 2025 at 7:32 PM Ryan Schmitt <[email protected]> wrote: > > > I ran our internal integration test suite against the current core+client > > commits. I didn't find much, just two notes: > > > > 1. The async client has started decompressing responses. I had to add a > > call to `.disableContentCompression()`. This API is new in 5.6. This may > be > > an issue for libraries that use the async client, since it makes it > harder > > to "straddle" multiple versions of the client and obtain consistent > > behavior from all of them. > > 2. Our tests for insecure mode SSL (self-signed certs, obsolete TLS > > versions, etc) started failing. I had to fix this by adding a > > `HostnameVerificationPolicy.CLIENT` argument to the > > `DefaultClientTlsStrategy` constructor call, in addition to the custom > > `HostnameVerifier` I am already supplying. I think this must have been > > caused by a constructor delegation change in `DefaultClientTlsStrategy`, > > where the default policy was changed from `CLIENT` to `null` (which later > > gets turned into `BOTH`). > > >
