RE: [VOTE] Pulsar Client C++ Release 3.1.1 Candidate 2

2023-01-23 Thread Masahiro Sakamoto
+1 (binding) * Verified checksums and signatures * Successfully compiled the source code * Confirmed that producer and consumer work properly Thanks, Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From: Matteo Merli Sent: Tuesday, January 24, 202

[VOTE] Pulsar Client C++ Release 3.1.1 Candidate 2

2023-01-23 Thread Matteo Merli
This is the first release candidate for Apache Pulsar Client C++, version 3.1.1. It fixes the following issues: https://github.com/apache/pulsar-client-cpp/issues?q=label%3Arelease%2F3.1.1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note

Re: [VOTE] Pulsar Client C++ Release 3.1.1 Candidate 1

2023-01-23 Thread Matteo Merli
Thanks, I'm canceling this vote, and I'll send out an RC-2 quickly. -- Matteo Merli On Mon, Jan 23, 2023 at 5:42 AM Yunze Xu wrote: > > It makes sense to me, I have cherry-picked it to branch-3.1 now. I > think we need to open another candidate for it. > > Thanks, > Yunze > > On Mon, Jan 23,

Re: [ANNOUNCE] Nicolò Boschi as new PMC member in Apache Pulsar

2023-01-23 Thread Zixuan Liu
Congrats, Nicolò! Best, Zixuan Dave Fisher 于2023年1月21日周六 06:01写道: > Congratulations Nicolo! > > Best, > Dave > > > On Jan 20, 2023, at 6:57 AM, tison wrote: > > > > Congrats Nico! And well deserved :) > > > > Best, > > tison. > > > > > > Christophe Bornet 于2023年1月20日周五 22:39写道: > > > >> Congr

Re: [VOTE] Pulsar Client C++ Release 3.1.1 Candidate 1

2023-01-23 Thread Yunze Xu
It makes sense to me, I have cherry-picked it to branch-3.1 now. I think we need to open another candidate for it. Thanks, Yunze On Mon, Jan 23, 2023 at 4:34 PM Masahiro Sakamoto wrote: > > Hi Matteo, > > I faced an issue that a segmentation fault occurred when running a Node.js > application w

Re: [VOTE] PIP-236: Record schema in the request and carry to the broker when subscribing with AUTO_CONSUME schema.

2023-01-23 Thread Enrico Olivelli
+1 (binding) Enrico Il giorno lun 23 gen 2023 alle ore 14:44 Yunze Xu ha scritto: > > +1 (binding) > > Thanks, > Yunze > > On Fri, Jan 20, 2023 at 7:06 PM SiNan Liu wrote: > > > > Hello community, > > > > I'm starting the VOTE for PIP-236: Record schema in the request and carry > > to the broke

Re: [VOTE] PIP-236: Record schema in the request and carry to the broker when subscribing with AUTO_CONSUME schema.

2023-01-23 Thread Yunze Xu
+1 (binding) Thanks, Yunze On Fri, Jan 20, 2023 at 7:06 PM SiNan Liu wrote: > > Hello community, > > I'm starting the VOTE for PIP-236: Record schema in the request and carry > to the broker when subscribing with AUTO_CONSUME schema. > > PIP link: > https://github.com/apache/pulsar/issues/19113

Re: [VOTE] PIP-243: Register Jackson Java 8 support modules by default

2023-01-23 Thread Lari Hotari
I'm closing the vote for PIP-243. Thanks for the participation. Vote result +5 (+3 binding, +2 other) "PIP-243: Register Jackson Java 8 support modules by default" is now accepted. I have also updated the status in the list of PIPs at https://github.com/apache/pulsar/wiki. -Lari On 2023/01/16

Re: [VOTE] PIP-243: Register Jackson Java 8 support modules by default

2023-01-23 Thread Lari Hotari
+1 (binding) -Lari On 2023/01/16 10:16:05 Lari Hotari wrote: > Hello community, > > I'm starting the VOTE for PIP-243: Register Jackson Java 8 support modules by > default. > > Motivation: > Jackson has a separate Java 8 support modules for adding support for proper > serialization and deser

Re: [DISCUSS] Registering Jackson Java 8 support modules by default for all Pulsar components, including client

2023-01-23 Thread Lari Hotari
A potential breaking change would be the case when Java 8 support module hasn't been registered and Jackson seems to serialize and de-serialize the objects successfully, but with a obscure JSON structure. Jackson 2.12 introduced a solution to prevent this from happening for Java 8 date/time typ

RE: [VOTE] Pulsar Client C++ Release 3.1.1 Candidate 1

2023-01-23 Thread Masahiro Sakamoto
Hi Matteo, I faced an issue that a segmentation fault occurred when running a Node.js application with the following combinations: - Node.js v18 - Pulsar Node.js client v1.7.0 (wraps C++ client) - Pulsar C++ client v3.1.0 This issue seems to be caused by the symbols of the libraries included in