RichJacobs opened a new issue #87:
URL: https://github.com/apache/pulsar-dotpulsar/issues/87
Hi there, I cloned the repo, built locally (using VS 2019) and try to run
the tests. Unit tests but the integration tests just ran and ran until I
stopped them. I then try to run the sample project
danielorf commented on pull request #161:
URL: https://github.com/apache/pulsar-helm-chart/pull/161#issuecomment-917026692
v2.8.0 is currently blocked ([related
PR](https://github.com/apache/pulsar-helm-chart/pull/130)), is v2.8.1 reliant
on v2.8.0 being released first?
--
This is an au
frankjkelly commented on pull request #152:
URL: https://github.com/apache/pulsar-helm-chart/pull/152#issuecomment-916817363
@josephglanville that was my screw-up - apologies. @codelipenghui can you
help? Thanks!
--
This is an automated message from the Apache Git Service.
To respond to
Il giorno ven 10 set 2021 alle ore 11:38 r...@apache.org <
ranxiaolong...@gmail.com> ha scritto:
> > Creating a tag on the git repo is not enough to say that we cut a
> release,
> > but for how this stuff works it makes the chart
> > usable from users and we must take this into consideration as an
> Creating a tag on the git repo is not enough to say that we cut a release,
> but for how this stuff works it makes the chart
> usable from users and we must take this into consideration as an "official
> release".
Yes, I fully recognize that in pulsar-go-client, creating a tag can already
meet o
fengtao1998 commented on pull request #21:
URL: https://github.com/apache/pulsar-test-infra/pull/21#issuecomment-916770297
@eolivelli @timmyyuan PTAL
--
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
Xiaolong,
Thanks for your information, very useful.
I believe that we could make this better (and probably we "must").
Cutting a "release" in the ASF is a more involved and formal process.
Releasing a project must run through a formal validation process, and must
be validated by the PMC of the pr
Hello Enrico:
The current release of pulsar-helm-chart does not have a related process to
illustrate this.
In a conventional way, each release owner will push the related docker
image to the docker hub after each release is completed. At this time, we
will go to pulsar-helm-chart to open a new pr
LGTM +1
--
Thanks
Xiaolong Ran
PengHui Li 于2021年9月9日周四 下午10:18写道：
> LGTM +1
>
> On Thu, Sep 9, 2021 at 9:22 PM Jia Zhai wrote:
>
> > +1
> >
> > Best Regards.
> >
> >
> > Jia Zhai
> >
> > Beijing, China
> >
> > Mobile: +86 15810491983
> >
> >
> >
> >
> > On Thu, Sep 9, 2021 at 3:20 PM Enrico Ol
On 2021/09/10 06:22:09, PengHui Li wrote:
> Looks good overall,
>
> Do we need to consider the batch filter since the API is defined as
> `Message`, not `Entry`, so parts of the batch need to filter out, does it
> should be handled by Filter, or the consumer side, or the producer side?
>
> T
Hello everyone:
I wrote a proposal to enhance the functionality of ReconsumeLater, the
specific content is as follows:
---
# PIP 94: Support level increment delay for ReconsumerLater interface
- Status: Draft
- Author: Xiaolong Ran
- Pull request:
- Mailing list discussion:
- Release:
The purp
sourabhaggrawal opened a new pull request #420:
URL: https://github.com/apache/pulsar-manager/pull/420
Fixes #419
*(or if this PR is one task of a github issue, please add `Master Issue:
#` to link to the master issue.)*
Master Issue: #
### Motivation
Ten
fengtao1998 opened a new pull request #21:
URL: https://github.com/apache/pulsar-test-infra/pull/21
A script that automatically checks the document label of the pull request
and runs in the pulsar community.
Add tags according to the description of the pull request.
When the
13 matches
Mail list logo
