MarvinCai removed a comment on issue #154:
URL:
https://github.com/apache/pulsar-helm-chart/issues/154#issuecomment-979751473
I think you mean loki and prometheus, I'll work on adding option to enable
persistent storage for loki and prometheus.
--
This is an automated message from the A
Just put an update here. We have done the PR cherry-picking
https://github.com/apache/pulsar/commits/branch-2.7
And most of the integration tests are fixed due to the docker image issue
or the testcontainer issue, now some integration tests get passed, but some
are not.
And there are some failed
lhotari closed pull request #187:
URL: https://github.com/apache/pulsar-helm-chart/pull/187
--
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 #187:
URL: https://github.com/apache/pulsar-helm-chart/pull/187#issuecomment-991752452
Well, just realized that the Apache Pulsar Helm Chart doesn't provide an
option for using the process runtime. I don't think this PR is needed. The
previous workaround i
Hi,
Issue has been created at : https://github.com/apache/pulsar/issues/13244
Cheers,
Yufei
On Sun, 12 Dec 2021 at 00:45, Yunze Xu wrote:
> Looks good. Could you open an issue for it so we can add it later?
>
> Thanks,
> Yunze
> > 2021年12月10日 下午8:27，Yufei Zhang 写道：
> >
> > From what I read it
Totally agree
PengHui Li 於 2021年12月12日 週日 08:28 寫道：
> +1
>
> Penghui
>
> Matteo Merli 于2021年12月11日 周六15:28写道：
>
> > At this point, if 2.9.0 is non stable, I think we should fast-forward
> > to 2.9.1 which will include security fix. Though, we should start
> > 2.9.1 right now.
> >
> >
> > --
> >
+1
Penghui
Matteo Merli 于2021年12月11日 周六15:28写道：
> At this point, if 2.9.0 is non stable, I think we should fast-forward
> to 2.9.1 which will include security fix. Though, we should start
> 2.9.1 right now.
>
>
> --
> Matteo Merli
>
>
> On Fri, Dec 10, 2021 at 11:23 PM Michael Marshall
> wrote
lhotari commented on pull request #187:
URL: https://github.com/apache/pulsar-helm-chart/pull/187#issuecomment-991752452
Well, just realized that the Apache Pulsar Helm Chart doesn't provide an
option for using the process runtime. I don't think this PR is needed. The
previous workaround i
lhotari closed pull request #187:
URL: https://github.com/apache/pulsar-helm-chart/pull/187
--
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 opened a new pull request #187:
URL: https://github.com/apache/pulsar-helm-chart/pull/187
### Motivation
- required for disabling the vulnerable feature in Pulsar Functions when
using the process runtime
### Additional context
- please notice that for mitigating
Looks good. Could you open an issue for it so we can add it later?
Thanks,
Yunze
> 2021年12月10日 下午8:27，Yufei Zhang 写道：
>
> From what I read it can be used in Maven projects. Basically it needs a
> SonarScanner (different versions for multiple languages and build tools)
> for Maven as in [1]. Then
For mitigating current systems, there's one more Log4JShell mitigation
strategy which is explained in
https://twitter.com/brunoborges/status/1469462412679991300 . This relies on
setting an environment variable called LOG4J_FORMAT_MSG_NO_LOOKUPS to the
value of "true" .
I created a simple test appl
Hi Michael,
+1,
Thanks for the great work.
We will continue on the PR cherry-picking and the release process to make
sure the urgent release can be done ASAP.
Penghui
On Sat, Dec 11, 2021 at 3:42 PM Michael Marshall
wrote:
> Given the log4j CVE, we should work to release 2.7.4.
>
> I started
13 matches
Mail list logo
