The Signature failed to verify
```
~/Downloads/release_2.9.2 » gpg --verify apache-pulsar-2.9.2-bin.tar.gz.asc
gpg: assuming signed data in 'apache-pulsar-2.9.2-bin.tar.gz'
gpg: Signature made Sat Jan 22 21:28:07 2022 CST
gpg:using RSA key 9F6FE6F28CC92CCB54B4E6F6C54B95E1C9106DA3
g
Sorry, the package has the wrong sign certificate. I'll close the rc1 for 2.9.2
and open start the rc2.
On 2022/01/24 09:33:32 PengHui Li wrote:
> The Signature failed to verify
>
> ```
> ~/Downloads/release_2.9.2 » gpg --verify apache-pulsar-2.9.2-bin.tar.gz.asc
> gpg: assuming signed data in '
pellicano commented on a change in pull request #205:
URL: https://github.com/apache/pulsar-helm-chart/pull/205#discussion_r790813294
##
File path: charts/pulsar/templates/broker-configmap.yaml
##
@@ -43,6 +43,62 @@ data:
zooKeeperSessionTimeoutMillis: "3"
statusFileP
pellicano commented on pull request #205:
URL:
https://github.com/apache/pulsar-helm-chart/pull/205#issuecomment-1020176850
Addressed security concern related to AWS and Azure credentials.
Let me know if there's else.
--
This is an automated message from the Apache Git Service.
To res
pellicano edited a comment on pull request #205:
URL:
https://github.com/apache/pulsar-helm-chart/pull/205#issuecomment-1020176850
Addressed security concern related to AWS and Azure credentials.
Let me know if there's anything else.
--
This is an automated message from the Apache Git
Congratulations!
Penghui
On Fri, Jan 21, 2022 at 6:17 PM Yu wrote:
> Congratulations! And thanks for contributing docs!
>
> On Fri, Jan 21, 2022 at 4:36 PM ZhangJian He wrote:
>
> > Congratulations!
> >
> > Thanks
> > ZhangJian He
> >
> > Enrico Olivelli 于2022年1月21日周五 15:42写道：
> >
> > > Congr
Good.
I will send an email to u...@pulsar.apache.org that states the EOL
status for 2.6
Enrico
Il giorno lun 10 gen 2022 alle ore 19:26 Chris Herzog
ha scritto:
>
> I agree with 2.6 EOL.
>
> On Mon, Jan 10, 2022 at 2:35 AM Enrico Olivelli wrote:
>
> > This thread is now to moving branch-2.6 (th
Hello,
This message is to formally announce the 2.6 release line, together
with all of the previous release lines (2.5, 2.4...) reached
End-Of-Line status.
This basically this means that:
- we are not going to cut new releases for 2.6
- users are encouraged to move to 2.7 or later
Best regards
En
michaeljmarshall commented on issue #441:
URL: https://github.com/apache/pulsar-manager/issues/441#issuecomment-1020387920
@mattisonchao - yes, that makes sense to me for docker-compose. Ideally, we
will also make it configurable in the pulsar helm chart.
--
This is an automated message
Thanks for your participation.
Close the vote with 3 (+1) bindings and 1 (+1) non-bindings.
On Fri, Jan 21, 2022 at 3:19 PM 陳智弘 wrote:
> +1
>
> Niclas Hedhman 於 2022年1月22日 週六 05:27 寫道：
>
> >
> > +1, non-binding
> >
> > On 2022-01-21 21:07, Neng Lu wrote:
> > > Hi All,
> > >
> > > I would like t
ericsyh opened a new pull request #209:
URL: https://github.com/apache/pulsar-helm-chart/pull/209
Signed-off-by: Eric Shen
### Motivation
Fix the missing EOF on bk statefulset template.
### Modifications
Add the missing EOF on bk sts.
### Verifying this c
lhotari merged pull request #208:
URL: https://github.com/apache/pulsar-helm-chart/pull/208
--
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-un
lhotari closed pull request #209:
URL: https://github.com/apache/pulsar-helm-chart/pull/209
--
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-un
lhotari commented on pull request #209:
URL:
https://github.com/apache/pulsar-helm-chart/pull/209#issuecomment-1020832918
@ericsyh This problem is already fixed by #208 . I have merged it now. I'll
close this PR.
--
This is an automated message from the Apache Git Service.
To respond to
> Yes, but it doesn't seem like a big deal.
I mentioned it to identify a subtle implication of the proposed
design. I think we should be intentional about what we expose
to end users.
By putting this field in the protobuf, we will have more control
over how users interact with this feature.
> We
I have no objection to adding new fields,
We should have no other disagreements in other respects by now,
Zike, could you please help start the new VOTE email thread for this
proposal?
Regards,
Penghui
On Tue, Jan 25, 2022 at 2:46 PM Michael Marshall
wrote:
> > Yes, but it doesn't seem like a
Matt-Esch opened a new issue #191:
URL: https://github.com/apache/pulsar-client-node/issues/191
Attempting to connect to a local standalone pulsar container using token
based auth, pulsar-client-node installed at 1.5.0, local pulsar installed at
2.9.1 and node 16.13.2 / npm 8.3.0.
`
Matt-Esch commented on issue #99:
URL:
https://github.com/apache/pulsar-client-node/issues/99#issuecomment-1020882307
Segfault issue tracked here:
https://github.com/apache/pulsar-client-node/issues/191
--
This is an automated message from the Apache Git Service.
To respond to the mess
What's the status of this PIP ?
We have a pending PR,
we can commit it as soon as the VOTE thread is officially closed
https://github.com/apache/pulsar/pull/13341
Il giorno gio 23 dic 2021 alle ore 01:17 Sijie Guo
ha scritto:
>
> +1
>
> On Tue, Dec 21, 2021 at 3:22 PM Matteo Merli wrote:
>
> >
ericsyh commented on pull request #209:
URL:
https://github.com/apache/pulsar-helm-chart/pull/209#issuecomment-1020897852
> @ericsyh This problem is already fixed by #208 . I have merged it now.
I'll close this PR.
OK, sure.
--
This is an automated message from the Apache Git Ser
This sounds quite important, and I would like to hear from the devs if
this is correct or something is misunderstood. I am about to recommend
(or not) a critical multi-tenant system, so would like to get the full
picture.
Thanks
Niclas
On 2022-01-21 15:51, Devin Bost wrote:
I discovered th
The only recommended way to run a multi-tenant Pulsar functions
clusters is to run it with Kubernetes runtime.
In thread or process runtime, there is no reliable way to restrict the
access to the credentials of each function instance (since it needs to
be readable by the same unix user), or for wh
22 matches
Mail list logo
