Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.6 Candidate 1

Hi Yunze, Yes this is expected. On the source validation (https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation) the "diff" results always include the gradle pieces. For example: Only in pulsar-client-reactive-0.5.6-candidate-1-source/gradle: wrapper Only in

Re: [VOTE] PIP-358: let resource weight work for OverloadShedder, LeastLongTermMessageRate, ModularLoadManagerImpl.

+1 (binding) Thanks, Yunze On Fri, Jun 14, 2024 at 8:30 PM guo jiwei wrote: > > +1 (binding) > > > Regards > Jiwei Guo (Tboy) > > > On Fri, Jun 14, 2024 at 11:04 AM Yubiao Feng > wrote: > > > +1 (binding) > > > > Thanks > > Yubiao Feng > > > > On Fri, Jun 14, 2024 at 10:09 AM thetumbled wrote:

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.6 Candidate 1

I noticed the `gradlew` and `gradlew.bat` files are missing. Is it expected? Thanks, Yunze On Thu, Jun 13, 2024 at 10:37 PM Lari Hotari wrote: > > +1 (binding) > > Validated source artifacts > - checked sha512 checksum > - checked signature > > Validated binaries > - ran sample app > > -Lari > >

[DISCUSS] PIP-361: Support URI, DNS, RID, IP based Token building from client's X.509 Certificate SAN Extensions

Hello, This is my PIP Request at https://github.com/apache/pulsar/pull/22917 If this PIP is acceptable, i am considering the following for the code changes: 1. Enhance the existing org.apache.pulsar.broker.authentication.AuthenticationProviderTls class to support these changes 2. Cre