[GitHub] [pulsar-dotpulsar] kandersen82 opened a new pull request #90: Change default behaviour on MetaDataException
kandersen82 opened a new pull request #90: URL: https://github.com/apache/pulsar-dotpulsar/pull/90 Error occurs when tenant or namespace supplied in topic string does not exist. org.apache.pulsar.broker.web.RestException: Policies not found for tenant/namespace namespace -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-dotpulsar] blankensteiner merged pull request #90: Change default behaviour on MetaDataException
blankensteiner merged pull request #90: URL: https://github.com/apache/pulsar-dotpulsar/pull/90 -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[CANCELLED] [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1
Hi Dave, Thank you for pointing it out. I had a lack of understanding of the release policy, sorry. I'm going to cancel this vote. Regards, Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From: Dave Fisher Sent: Tuesday, October 12, 2021 3:27 PM To: dev@pulsar.apache.org Subject: Re: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1 > On Oct 8, 2021, at 3:20 AM, Masahiro Sakamoto wrote: > > This is the first release candidate for Apache Pulsar Node.js client, version > 1.3.2. > > It fixes the following issues: > https://github.com/apache/pulsar-client-node/milestone/9?closed=1 > > *** Please download, test and vote on this release. This vote will > stay open for at least 72 hours *** > > Note that we are voting upon the source (tag), the npm package is > provided for convenience. > > The tag to be voted upon: > v1.3.2-rc.1 > https://github.com/apache/pulsar-client-node/releases/tag/v1.3.2-rc.1 -1 (binding) we don’t vote on tags. We vote on signed packages that also have checksums. https://www.apache.org/legal/release-policy.html#policy https://infra.apache.org/release-publishing.html#definition > > The npm package: > https://www.npmjs.com/package/pulsar-client/v/1.3.2-rc.1 > > Please download the source files, and follow the README to build and > run the Pulsar Node.js client. > > Masahiro Sakamoto > Yahoo Japan Corp. > E-mail: massa...@yahoo-corp.jp
[CANCELLED] [VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1
Hi Dave, Thank you for pointing it out. I had a lack of understanding of the release policy, sorry. I'm going to cancel this vote. Regards, Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From: Dave Fisher Sent: Tuesday, October 12, 2021 3:28 PM To: dev@pulsar.apache.org Subject: Re: [VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1 > On Oct 8, 2021, at 3:23 AM, Masahiro Sakamoto wrote: > > This is the first release candidate for Apache Pulsar Node.js client, version > 1.4.1. > > It fixes the following issues: > https://github.com/apache/pulsar-client-node/milestone/10?closed=1 > > *** Please download, test and vote on this release. This vote will stay open > for at least 72 hours *** > > Note that we are voting upon the source (tag), the npm package is provided > for convenience. > > The tag to be voted upon: > v1.4.1-rc.1 > https://github.com/apache/pulsar-client-node/releases/tag/v1.4.1-rc.1 -1 (binding) we don’t vote on tags. We vote on signed packages that also have checksums. https://www.apache.org/legal/release-policy.html#policy https://infra.apache.org/release-publishing.html#definition > > The npm package: > https://www.npmjs.com/package/pulsar-client/v/1.4.1-rc.1 > > Please download the source files, and follow the README to build > and run the Pulsar Node.js client. > > Masahiro Sakamoto > Yahoo Japan Corp. > E-mail: massa...@yahoo-corp.jp
RE: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1
Thank you Enrico. I will upload the tarball and other files to dist and then run the vote again. Regards, Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp -Original Message- From: Enrico Olivelli Sent: Tuesday, October 12, 2021 3:50 PM To: Dev Subject: Re: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1 Masahiro, I suggest to create a .tar.gz file with the contents of the release, only source files and copy it to the staging repository https://dist.apache.org/repos/dist/dev/pulsar/ No need to add commits to the repo I believe that if you do this we can continue on the VOTE We should also update the release procedure Thank you for being the Release Manager Enrico Il giorno mar 12 ott 2021 alle ore 08:27 Dave Fisher ha scritto: > > > > On Oct 8, 2021, at 3:20 AM, Masahiro Sakamoto > wrote: > > > > This is the first release candidate for Apache Pulsar Node.js client, > version 1.3.2. > > > > It fixes the following issues: > > https://github.com/apache/pulsar-client-node/milestone/9?closed=1 > > > > *** Please download, test and vote on this release. This vote will stay > open > > for at least 72 hours *** > > > > Note that we are voting upon the source (tag), the npm package is > provided > > for convenience. > > > > The tag to be voted upon: > > v1.3.2-rc.1 > > https://github.com/apache/pulsar-client-node/releases/tag/v1.3.2-rc.1 > > -1 (binding) we don’t vote on tags. We vote on signed packages that also > have checksums. > > https://www.apache.org/legal/release-policy.html#policy > https://infra.apache.org/release-publishing.html#definition > > > > > The npm package: > > https://www.npmjs.com/package/pulsar-client/v/1.3.2-rc.1 > > > > Please download the source files, and follow the README to build > > and run the Pulsar Node.js client. > > > > Masahiro Sakamoto > > Yahoo Japan Corp. > > E-mail: massa...@yahoo-corp.jp > >
[GitHub] [pulsar-manager] pgandhap opened a new issue #425: Install Pulsar-manager on kubernetes cluster
pgandhap opened a new issue #425:
URL: https://github.com/apache/pulsar-manager/issues/425
Iam wanna to use pulsar-manager for GUI management, monitoring tool and
following this
https://pulsar.apache.org/docs/en/administration-pulsar-manager/. In this on
step ( Set administrator account and password ) , when i ran -> curl -H
'X-XSRF-TOKEN: $CSRF_TOKEN' -H 'Cookie: XSRF-TOKEN=$CSRF_TOKEN;' -H
"Content-Type: application/json" -X PUT
http://localhost:7750/pulsar-manager/users/superuser -d '{"name": "admin",
"password": "apachepulsar", "description": "test", "email":
"usern...@test.org"}' this cmd it throws error with below
curl: (6) Could not resolve host: $CSRF_TOKEN'
curl: (6) Could not resolve host: XSRF-TOKEN=$CSRF_TOKEN;'
{"timestamp":"2021-10-12T03:27:07.419+","status":403,"error":"Forbidden","message":"Forbidden","path":"/pulsar-manager/users/superuser"}curl:
(6) Could not resolve host: admin,
curl: (6) Could not resolve host: password
curl: (6) Could not resolve host: apachepulsar,
curl: (6) Could not resolve host: description
curl: (6) Could not resolve host: test,
curl: (6) Could not resolve host: email
curl: (3) [globbing] unmatched close brace/bracket in column 18
**Can anyone help on this** .
--
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...@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1
This is the first release candidate for Apache Pulsar Node.js client, version 1.3.2. The artifacts are exactly the same as the first vote, but I didn't upload them and the signature to the staging repository of dist, so I'll run the vote again. It fixes the following issues: https://github.com/apache/pulsar-client-node/milestone/9?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag), the npm package is provided for convenience. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node-1.3.2-candidate-1/ SHA-512 checksum: 5f6c7e1a096a3ae66eee71c552af89532ed86bf94da3f3d49836c080426ee5dcaabeda440a989d51772d2e67e2dca9539ea83cfbc7c2a0847a0ec04b310f v1.3.2-rc.1.tar.gz The tag to be voted upon: v1.3.2-rc.1 https://github.com/apache/pulsar-client-node/releases/tag/v1.3.2-rc.1 The npm package: https://www.npmjs.com/package/pulsar-client/v/1.3.2-rc.1 Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS Please download the source files, and follow the README to build and run the Pulsar Node.js client. Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp
[VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1
This is the first release candidate for Apache Pulsar Node.js client, version 1.4.1. The artifacts are exactly the same as the first vote, but I didn't upload them and the signature to the staging repository of dist, so I'll run the vote again. It fixes the following issues: https://github.com/apache/pulsar-client-node/milestone/10?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag), the npm package is provided for convenience. Source files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node-1.4.1-candidate-1/ SHA-512 checksum: b011b20e337af01542e2d9d3f6e74b8f506fab9b29227c8447f263e15103944bcb37a14643e4bcfa3286ec05c4d00f2d210708d6c06cb5851004ce099f77fcaf v1.4.1-rc.1.tar.gz The tag to be voted upon: v1.4.1-rc.1 https://github.com/apache/pulsar-client-node/releases/tag/v1.4.1-rc.1 The npm package: https://www.npmjs.com/package/pulsar-client/v/1.4.1-rc.1 Pulsar's KEYS file containing PGP keys we use to sign the release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS Please download the source files, and follow the README to build and run the Pulsar Node.js client. Masahiro Sakamoto Yahoo Japan Corp. E-mail: massa...@yahoo-corp.jp
Re: [VOTE] Pulsar Node.js Client Release 1.3.2 Candidate 1
+1 (binding) * check the license headers * install the npm package * build the source and run producer/consumer * verify checksum and signatures Thanks, Nozomi 2021年10月12日(火) 19:20 Masahiro Sakamoto : > This is the first release candidate for Apache Pulsar Node.js client, > version 1.3.2. > > The artifacts are exactly the same as the first vote, but I didn't upload > them and the signature > to the staging repository of dist, so I'll run the vote again. > > It fixes the following issues: > https://github.com/apache/pulsar-client-node/milestone/9?closed=1 > > *** Please download, test and vote on this release. This vote will stay > open > for at least 72 hours *** > > Note that we are voting upon the source (tag), the npm package is provided > for convenience. > > Source files: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node-1.3.2-candidate-1/ > > SHA-512 checksum: > 5f6c7e1a096a3ae66eee71c552af89532ed86bf94da3f3d49836c080426ee5dcaabeda440a989d51772d2e67e2dca9539ea83cfbc7c2a0847a0ec04b310f > v1.3.2-rc.1.tar.gz > > The tag to be voted upon: > v1.3.2-rc.1 > https://github.com/apache/pulsar-client-node/releases/tag/v1.3.2-rc.1 > > The npm package: > https://www.npmjs.com/package/pulsar-client/v/1.3.2-rc.1 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Please download the source files, and follow the README to build > and run the Pulsar Node.js client. > > Masahiro Sakamoto > Yahoo Japan Corp. > E-mail: massa...@yahoo-corp.jp >
Re: [VOTE] Pulsar Node.js Client Release 1.4.1 Candidate 1
+1 (binding) * check the license headers * install the npm package * build the source and run producer/consumer * verify checksum and signatures Thanks, Nozomi 2021年10月12日(火) 19:26 Masahiro Sakamoto : > This is the first release candidate for Apache Pulsar Node.js client, > version 1.4.1. > > The artifacts are exactly the same as the first vote, but I didn't upload > them and the signature > to the staging repository of dist, so I'll run the vote again. > > It fixes the following issues: > https://github.com/apache/pulsar-client-node/milestone/10?closed=1 > > *** Please download, test and vote on this release. This vote will stay > open > for at least 72 hours *** > > Note that we are voting upon the source (tag), the npm package is provided > for convenience. > > Source files: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-node-1.4.1-candidate-1/ > > SHA-512 checksum: > b011b20e337af01542e2d9d3f6e74b8f506fab9b29227c8447f263e15103944bcb37a14643e4bcfa3286ec05c4d00f2d210708d6c06cb5851004ce099f77fcaf > v1.4.1-rc.1.tar.gz > > The tag to be voted upon: > v1.4.1-rc.1 > https://github.com/apache/pulsar-client-node/releases/tag/v1.4.1-rc.1 > > The npm package: > https://www.npmjs.com/package/pulsar-client/v/1.4.1-rc.1 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Please download the source files, and follow the README to build > and run the Pulsar Node.js client. > > Masahiro Sakamoto > Yahoo Japan Corp. > E-mail: massa...@yahoo-corp.jp >
[GitHub] [pulsar-helm-chart] frankjkelly commented on pull request #165: useV2WireProtocol for bookkeeper autorecovery
frankjkelly commented on pull request #165: URL: https://github.com/apache/pulsar-helm-chart/pull/165#issuecomment-940988386 Just for my information can someone explain why Autorecovery should use the V2 protocol but the Broker V3? Thanks in advance! -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-helm-chart] frankjkelly closed pull request #159: Fix #152 Helm chart does not support Istio port naming
frankjkelly closed pull request #159: URL: https://github.com/apache/pulsar-helm-chart/pull/159 -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-helm-chart] frankjkelly commented on issue #164: 2.7.3 helm chart still use 2.7.2 images
frankjkelly commented on issue #164: URL: https://github.com/apache/pulsar-helm-chart/issues/164#issuecomment-941032822 This was due to my change where I rev'd the Chart version https://github.com/apache/pulsar-helm-chart/commit/5b10f48f5b271a15c000239042c507c33da16fe9 (unfortunately semver does not support a bug-fix release e.g. `2.7.2.1`) -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-helm-chart] eolivelli commented on pull request #165: useV2WireProtocol for bookkeeper autorecovery
eolivelli commented on pull request #165: URL: https://github.com/apache/pulsar-helm-chart/pull/165#issuecomment-941064004 if you want to leverage ExplicitLAC feature you need V3, so it is better to use V3 on the broker. AutoRecovery needs only to read/write to the bookies, no need for ExplicitLAC API -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-helm-chart] frankjkelly commented on pull request #165: useV2WireProtocol for bookkeeper autorecovery
frankjkelly commented on pull request #165: URL: https://github.com/apache/pulsar-helm-chart/pull/165#issuecomment-941069144 Thanks @eolivelli ! -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-helm-chart] hangc0276 commented on pull request #165: useV2WireProtocol for bookkeeper autorecovery
hangc0276 commented on pull request #165: URL: https://github.com/apache/pulsar-helm-chart/pull/165#issuecomment-941868430 > Just for my information can someone explain why Autorecovery should use the V2 protocol but the Broker V3? Thanks in advance! @frankjkelly I broker side, it has been set the bookie client use V2 protocol by default. -- 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...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[VOTE] PIP - Support pluggable entry filter in Dispatcher
Hi Pulsar Community, I would like to start a VOTE for PIP - Support pluggable entry filter in Dispatcher. The issue for this PIP is here: https://github.com/apache/pulsar/issues/12269 Please VOTE within 72 hours. Thanks, Lin Lin
