Update for apachepulsar/pulsar-build images

2021-07-20 Thread Yunze Xu
Hello, Currently Pulsar's CI workflows rely on some docker images, but I found these images are maintained mannually by who has the permission. See https://hub.docker.com/r/apachepulsar/pulsar-build/tags?page=1&ordering=last_updated If any Dockerfile changed, the image wouldn't be built and pushed

[GitHub] [pulsar-client-node] massakam merged pull request #163: Use Buffer::Copy instead of Buffer::New

2021-07-20 Thread GitBox
massakam merged pull request #163: URL: https://github.com/apache/pulsar-client-node/pull/163 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-

[GitHub] [pulsar-client-node] hrsakai commented on pull request #163: Use Buffer::Copy instead of Buffer::New

2021-07-20 Thread GitBox
hrsakai commented on pull request #163: URL: https://github.com/apache/pulsar-client-node/pull/163#issuecomment-883036429 > The following part doesn't need to be modified because ptr is not shared_ptr, right? This issue seems to occure if adding same pointer to `Napi::Buffer::New`,

[GitHub] [pulsar-manager] Huanli-Meng commented on pull request #403: Added chinese version..

2021-07-20 Thread GitBox
Huanli-Meng commented on pull request #403: URL: https://github.com/apache/pulsar-manager/pull/403#issuecomment-882972418 As confirmed with Guowei, he is responsible for updating the doc based on the cloud-manager doc (chinese version) and only review some uncovered contents. -- This

[GitHub] [pulsar-client-node] massakam commented on pull request #163: Use Buffer::Copy instead of Buffer::New

2021-07-20 Thread GitBox
massakam commented on pull request #163: URL: https://github.com/apache/pulsar-client-node/pull/163#issuecomment-883013636 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

Re: [DISCUSS] Releasing Pulsar-client-go 0.6.0

2021-07-20 Thread PengHui Li
+1 On Jul 20, 2021, 7:24 AM +0800, Ming Luo , wrote: > +1 > > Thanks > Ming > > On Mon, 19 Jul 2021 at 18:55, Neng Lu wrote: > > > +1 > > > > Neng Lu > > > > On 2021/07/19 08:44:11 "r...@apache.org" wrote: > > > Hello Everyone: > > > > > > I hope you’ve all been doing well. In the past two months

[GitHub] [pulsar-client-node] massakam merged pull request #163: Use Buffer::Copy instead of Buffer::New

2021-07-20 Thread GitBox
massakam merged pull request #163: URL: https://github.com/apache/pulsar-client-node/pull/163 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-

[GitHub] [pulsar-client-node] hrsakai commented on pull request #163: Use Buffer::Copy instead of Buffer::New

2021-07-20 Thread GitBox
hrsakai commented on pull request #163: URL: https://github.com/apache/pulsar-client-node/pull/163#issuecomment-883036429 > The following part doesn't need to be modified because ptr is not shared_ptr, right? This issue seems to occure if adding same pointer to `Napi::Buffer::New`,

[GitHub] [pulsar-manager] Huanli-Meng commented on pull request #403: Added chinese version..

2021-07-20 Thread GitBox
Huanli-Meng commented on pull request #403: URL: https://github.com/apache/pulsar-manager/pull/403#issuecomment-882972418 As confirmed with Guowei, he is responsible for updating the doc based on the cloud-manager doc (chinese version) and only review some uncovered contents. -- This

[GitHub] [pulsar-client-node] massakam commented on pull request #163: Use Buffer::Copy instead of Buffer::New

2021-07-20 Thread GitBox
massakam commented on pull request #163: URL: https://github.com/apache/pulsar-client-node/pull/163#issuecomment-883013636 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

Re: Re: Problems with Functions/IO in Upgrading Pulsar from 2.7 to 2.8

2021-07-20 Thread Enrico Olivelli
I have filed a PR with an update to the Release notes for 2.8.0 https://github.com/apache/pulsar/pull/11392 Thank you all for your feedback Enrico Il giorno mar 20 lug 2021 alle ore 00:54 Neng Lu ha scritto: > Based on my local test, it's fine for String Schema. > > On 2021/07/19 18:47:49 Devin

[VOTE] Pulsar Release 2.7.3 Candidate 1

2021-07-20 Thread 丛搏
This is the first release candidate for Apache Pulsar, version 2.7.3. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F2.7.3+is%3Apr+ *** Please download, test and vote on this release. This vote will stay open for at least 72 hours ***

Re: [VOTE] Pulsar Release 2.7.3 Candidate 1

2021-07-20 Thread PengHui Li
Hi, Bo Cong For the tag `v2.7.3-candidate-1`, the project version is `2.7.3-SNAPSHOT`. But for the `apache-pulsar-2.7.3-src.tar.gz`, the version is `2.7.3`. Have you pushed a commit for updating the project version? -1 Thanks, Penghui On Tue, Jul 20, 2021 at 9:17 PM 丛搏 wrote: > This is the fi

[Pulsar Community Weekly Update] 2021-07-12 ~ 2021-07-18

2021-07-20 Thread Huanli Meng
Dear Pulsar enthusiast, This is the Pulsar community weekly update for 2021-07-12 ~ 2021-07-18, with updates on Pulsar client, broker, and so on. This Pulsar community weekly update is also available at https://streamnative.io/weekly/2021/2021-07/2021-07-19-pulsar-weekly. All Pulsar community we

Join Pulsar talks in ApacheCon Asia 2021 and ApacheCon@Home 2021~

2021-07-20 Thread Jinfeng Huang
Hi Pulsar community, We are excited to see that ApacheCon Asia 2021 and ApacheCon@Home 2021 are almost here. This year you will find Apache Pulsar talks across a number of different tracks. We have highlighted some of the Pulsar talks below: ApacheCon Asia 2021 - August 6-8th - *Community*

Apache Pulsar domains

2021-07-20 Thread Aaron Williams
Hello all, I noticed that a number of Apache Pulsar domains were still available, so I purchased them to donate them to the community. Who do I need to contact to do that? The domains are apachepulsar.com, apachepulsar.io, and apachepulsar.org and are currently redirecting to pulsar.apache.org.

[GitHub] [pulsar-adapters] rdhabalia merged pull request #26: [pulsar-kafka] Support encryption for pulsar-kafka producer/consumer

2021-07-20 Thread GitBox
rdhabalia merged pull request #26: URL: https://github.com/apache/pulsar-adapters/pull/26 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsu

Re: Update for apachepulsar/pulsar-build images

2021-07-20 Thread Sijie Guo
Penghui can probably help you there. But I think it would be good to have CI jobs to publish those build images. - Sijie On Tue, Jul 20, 2021 at 1:18 AM Yunze Xu wrote: > > Hello, > Currently Pulsar's CI workflows rely on some docker images, but I found these > images are maintained mannually b

Re: [DISCUSS] Releasing Pulsar-client-go 0.6.0

2021-07-20 Thread Sijie Guo
+1 On Tue, Jul 20, 2021 at 4:16 AM PengHui Li wrote: > > +1 > On Jul 20, 2021, 7:24 AM +0800, Ming Luo , > wrote: > > +1 > > > > Thanks > > Ming > > > > On Mon, 19 Jul 2021 at 18:55, Neng Lu wrote: > > > > > +1 > > > > > > Neng Lu > > > > > > On 2021/07/19 08:44:11 "r...@apache.org" wrote: > >

Re: Join Pulsar talks in ApacheCon Asia 2021 and ApacheCon@Home 2021~

2021-07-20 Thread Anonymitaet _
Hi Jennifer, Thanks for putting this together. Pulsar adoption and community engagement skyrocketed globally. It is a great opportunity to share our best practice with industry peers. From: Jinfeng Huang Reply-To: "us...@pulsar.apache.org" Date: Wednesday, July 21, 2021 at 00:11 To: pulsar-us