Paulo Lopes

@vietj @smoell this is a netty upgrade related issue. Vert.x doesn't use any crypto libraries except the ones provided by the JDK, the initialization happens upstream in netty here: https://github.com/netty/netty/blob/a98c60283b38830607780e039c7dd52715ec5814/handler/src/main/java/io/netty/handler/ssl/BouncyCastleAlpnSslUtils.java...

I've added a comment upstream linking to this issue. I'm probably not the best one to address this one as I don't know the internals of BC and allowing/denying classes...

Hi @heubeck all net client options are vertx-core specific, changing them is probably not a good idea as they would introduce a major breaking change to users. The net client...

@aloserman you're used the pooled mode, which means that for each command, a connection is acquired from the pool, the command executed, and the connection returned to the pool. Given...

That could be possible. It would require having a new method in the top level `Redis` interface and propagate it to the connection after it's created.

@dependabot rebase

@dependabot rebase

Hi @akshaypatidar1999 thanks for your issue. This is indeed a highly requested feature. We can break the task into 2 areas: * have the cluster discovery code run as a...

One way to address this is to use: ``` CONFIG SET timeout 30 ``` Add idle connections will close after 30s of idling. This is what other libraries like jedis...

The key locator was previously and internal implementation detail. It was not correct according to redis. It now follows redis and still it's an internal implementation detail. Which use case...