[GitHub] [pulsar-dotpulsar] blankensteiner closed issue #111: Support - SendTimeout for Producer Client

2022-10-14 Thread GitBox
blankensteiner closed issue #111: Support - SendTimeout for Producer Client URL: https://github.com/apache/pulsar-dotpulsar/issues/111 -- 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 com

Re: [ANNOUNCE] New Committer: Qiang Huang

2022-10-14 Thread Jiaqi Shen
Congratulations! (Are you BUPTer?🤔 ) Thanks, Jiaqi Shen Jun Ma 于2022年10月14日周五 14:55写道: > Congratulations, Qiang! > > From: Xiangying Meng > Sent: Friday, October 14, 2022 14:17 > To: dev@pulsar.apache.org > Subject: Re: [ANNOUNCE] New Committer: Qiang Huang

Re: [ANNOUNCE] New Committer: Qiang Huang

2022-10-14 Thread Nicolò Boschi
Congrats! Nicolò Boschi Il giorno ven 14 ott 2022 alle ore 09:18 Jiaqi Shen ha scritto: > Congratulations! > > (Are you BUPTer?🤔 ) > > Thanks, > Jiaqi Shen > > > Jun Ma 于2022年10月14日周五 14:55写道: > > > Congratulations, Qiang! > > > > From: Xiangying Meng > > Sent

[GitHub] [pulsar-client-node] shibd opened a new pull request, #235: [feat] Napi support package c++ static binary.

2022-10-14 Thread GitBox
shibd opened a new pull request, #235: URL: https://github.com/apache/pulsar-client-node/pull/235 ### Motivation Currently, users using the `node js client` must first install the `C++ client`. And when the user executes `npm install`, it also needs to be compiled. This is not user-f

[GitHub] [pulsar-client-node] BewareMyPower commented on a diff in pull request #235: [feat] Napi support package c++ static binary.

2022-10-14 Thread GitBox
BewareMyPower commented on code in PR #235: URL: https://github.com/apache/pulsar-client-node/pull/235#discussion_r995500769 ## examples/encryption-consumer.js: ## @@ -32,7 +32,7 @@ const Pulsar = require('pulsar-client'); subscription: 'sub1', subscriptionType: 'Share

[GitHub] [pulsar-helm-chart] hpvd commented on issue #294: [security] helm chart is outdated and includes images with 992 vulnerabilities (623 fixable)

2022-10-14 Thread GitBox
hpvd commented on issue #294: URL: https://github.com/apache/pulsar-helm-chart/issues/294#issuecomment-1278684995 @michaeljmarshall many thanks for starting looking in it that fast and especially your proposal to make a general approach set the ground to finally solve this (https://githu

[GitHub] [pulsar-helm-chart] hpvd commented on issue #294: [security] helm chart is outdated and includes images with 992 vulnerabilities (623 fixable)

2022-10-14 Thread GitBox
hpvd commented on issue #294: URL: https://github.com/apache/pulsar-helm-chart/issues/294#issuecomment-1278686184 just as background info, the security scanner used by artifacthub, providing results shown above is trivy, **so all the finding should be pretty valid**. For details,

[GitHub] [pulsar-client-node] equanz commented on issue #78: Error: Failed to send message: AlreadyClosed

2022-10-14 Thread GitBox
equanz commented on issue #78: URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-1278689559 @jbmusso If batchingEnabled is false(default), Producer#flush does nothing. From C++ v2.8.2, pending messages fail when Producer#close is called. https://github.com/apa

[DISCUSS] Release Pulsar Client Node.js 3.0.0

2022-10-14 Thread Baodi Shi
Hi, We're releasing C++ and python 3.0.0 client, Node.js Client is also built on C++, and I'd like to discuss whether to start working on Node.js Client 3.0.0 as well. In Node.js 3.0.0 Client, I mainly want to make the following changes: 1. Users no longer need to install the C++ client when us

[GitHub] [pulsar-client-node] shibd commented on pull request #235: [feat] Napi support package c++ static binary.

2022-10-14 Thread GitBox
shibd commented on PR #235: URL: https://github.com/apache/pulsar-client-node/pull/235#issuecomment-1278692145 > Why do you rename the directory name from `certificate` to `test-conf`? Just for the unified, put all the test-related configurations together. -- This is an automated m

[GitHub] [pulsar-helm-chart] hpvd commented on pull request #299: Replace monitoring solution with kube-prometheus-stack dependency

2022-10-14 Thread GitBox
hpvd commented on PR #299: URL: https://github.com/apache/pulsar-helm-chart/pull/299#issuecomment-1278701720 just did the same check for the proposed stack at artifacthub. There are (like in every project) some vulnerabilities, but - much fewer than we have today - no damn old o

[GitHub] [pulsar-client-node] BewareMyPower commented on pull request #235: [feat] Napi support package c++ static binary.

2022-10-14 Thread GitBox
BewareMyPower commented on PR #235: URL: https://github.com/apache/pulsar-client-node/pull/235#issuecomment-1278700978 > Just for the unified There is no need to make two separate repositories consistent. What if the Python client repo renamed the directory or adjust the hierarchy la

Re: [ANNOUNCE] New Committer: Qiang Huang

2022-10-14 Thread r...@apache.org
Congratulations Qiang Huang -- Thanks XiaolongRan Nicolò Boschi 于2022年10月14日周五 15:23写道: > Congrats! > Nicolò Boschi > > > Il giorno ven 14 ott 2022 alle ore 09:18 Jiaqi Shen < > gleiphir2...@gmail.com> > ha scritto: > > > Congratulations! > > > > (Are you BUPTer?🤔 ) > > > > Thanks, > > Jiaqi Sh

RE: [VOTE] Pulsar Node.js Client Release 1.7.0 Candidate 2

2022-10-14 Thread Masahiro Sakamoto
Thanks Yuri. I agree with you and will change my vote to +1. +1 (binding) * Checked the license headers * Verified the checksum and signature * Built the source and ran producer/consumer Regards, Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From

[GitHub] [pulsar-helm-chart] hpvd commented on pull request #299: Replace monitoring solution with kube-prometheus-stack dependency

2022-10-14 Thread GitBox
hpvd commented on PR #299: URL: https://github.com/apache/pulsar-helm-chart/pull/299#issuecomment-1278733100 @michaeljmarshall since this will be some work and will probably trigger a major version bump, what do you think of releasing in the meantime a last updated version of 2.x - w

[GitHub] [pulsar-client-node] shibd commented on pull request #235: [feat] Napi support package c++ static binary.

2022-10-14 Thread GitBox
shibd commented on PR #235: URL: https://github.com/apache/pulsar-client-node/pull/235#issuecomment-1278797419 > From my perspective, if you have a huge PR, please remove unnecessary changes as much as possible. Make sense. I removed unnecessary changes. PTAL. -- This is an automa

[GitHub] [pulsar-dotpulsar] amareshmad commented on issue #114: When i run test console app consumer is creating and when i integrate same to actual product consumer is not creating and going to Fault

2022-10-14 Thread GitBox
amareshmad commented on issue #114: URL: https://github.com/apache/pulsar-dotpulsar/issues/114#issuecomment-1279135449 tried with setting VerifyCertificateAuthority ,VerifyCertificateName it didn't help. tried with setting registry as well didn't help. [HKEY_LOCAL_MACHINE\SOFTWARE

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on issue #290: Release Pulsar Helm Chart in GitHub Pages flavor

2022-10-14 Thread GitBox
michaeljmarshall commented on issue #290: URL: https://github.com/apache/pulsar-helm-chart/issues/290#issuecomment-1279300054 The airflow process is defined here https://github.com/apache/airflow/blob/main/dev/README_RELEASE_HELM_CHART.md. I will take a closer look at it and see if we can

Re: [DISCUSS] Release Pulsar Client Node.js 3.0.0

2022-10-14 Thread Matteo Merli
Hi Baodi, I'd suggest first getting the changes for pre-compiled binaries to be merged, tested, and expanded to support more combinations of os/cpu/nodejs. eg: mac-arm64, linux-alpine, etc.. Regarding the version number, 3.0 was adopted for C++ and Python because we had to detach from the main Pu

[GitHub] [pulsar-helm-chart] michaeljmarshall opened a new pull request, #300: Remove GitHub Action Workflows that release the chart

2022-10-14 Thread GitBox
michaeljmarshall opened a new pull request, #300: URL: https://github.com/apache/pulsar-helm-chart/pull/300 Relates to: https://github.com/apache/pulsar-helm-chart/issues/290 ### Motivation We should not use GitHub Actions to release the helm chart. As such, we can remove the r

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on a diff in pull request #274: Bump Apache Pulsar 2.10.1

2022-10-14 Thread GitBox
michaeljmarshall commented on code in PR #274: URL: https://github.com/apache/pulsar-helm-chart/pull/274#discussion_r996038428 ## charts/pulsar/Chart.yaml: ## @@ -18,10 +18,10 @@ # apiVersion: v2 -appVersion: "2.9.2" +appVersion: "2.10.1" description: Apache Pulsar Helm cha

[GitHub] [pulsar-helm-chart] michaeljmarshall merged pull request #284: Add nodeSelector to cluster initialize pod

2022-10-14 Thread GitBox
michaeljmarshall merged PR #284: URL: https://github.com/apache/pulsar-helm-chart/pull/284 -- 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-unsubscr.

Re: [DISCUSS] PIP-212: Default reppDnsResolverClass to ZkBookieRackAffinityMapping

2022-10-14 Thread Michael Marshall
For the sake of the VOTE, I am classifying this as a bug and plan to cherry pick it to all active release branches. Thanks, Michael On Tue, Oct 11, 2022 at 2:59 PM Michael Marshall wrote: > > Hi All, > > I created PIP 212: https://github.com/apache/pulsar/issues/18012. It > already has a PR http

[VOTE] PIP-212: Default reppDnsResolverClass to ZkBookieRackAffinityMapping

2022-10-14 Thread Michael Marshall
Hi All, I am starting the vote for PIP 212: Default reppDnsResolverClass to ZkBookieRackAffinityMapping. https://github.com/apache/pulsar/issues/18012 Here is the discussion thread: https://lists.apache.org/thread/188nq3vcs40cwdwj5z2jon0ryfqh3wbg The vote will be open for at least 3 days. Note

[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #114: When i run test console app consumer is creating and when i integrate same to actual product consumer is not creating and going to F

2022-10-14 Thread GitBox
blankensteiner commented on issue #114: URL: https://github.com/apache/pulsar-dotpulsar/issues/114#issuecomment-1279428552 It sounds like something is broken in the production app. Maybe some dependencies or settings are lingering from when it was .NET Framework 4.5. Possibly related to

Re: [VOTE] Pulsar Client C++ Release 3.0.0 Candidate 2

2022-10-14 Thread Matteo Merli
I'm canceling this vote again. There is an issue that was recently discovered, around an inconsistencies in the validation of topic names in C++ (compared with Java client and broker). PTAL: https://github.com/apache/pulsar-client-cpp/pull/52 I'll send out an rc-3 once this is merged. -- Matteo

[GitHub] [pulsar-helm-chart] michaeljmarshall opened a new pull request, #301: New Release Process

2022-10-14 Thread GitBox
michaeljmarshall opened a new pull request, #301: URL: https://github.com/apache/pulsar-helm-chart/pull/301 Fixes #290 ### Motivation Make the Apache Pulsar Helm Chart release follow ASF rules for voting, and make the helm binary available via dist.apache.org. By following the

[DISCUSS] Helm Chart Updates and Release Process

2022-10-14 Thread Michael Marshall
Hi Pulsar Community, I propose that we update our Helm Chart release process so that it follows the ASF guidelines. My proposed process is in this PR [0]. I built it by copying the Apache Airflow release process [1] and modifying it to fit the Apache Pulsar project. The git history shows my change

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on pull request #299: Replace monitoring solution with kube-prometheus-stack dependency

2022-10-14 Thread GitBox
michaeljmarshall commented on PR #299: URL: https://github.com/apache/pulsar-helm-chart/pull/299#issuecomment-1279519673 > @michaeljmarshall since this will be some work and will probably trigger a major version bump, what do you think of releasing in the meantime a last updated version of