Great work! Yunze.
There are a lot of work before current release process, maybe we should
also include these:
1. Start a discussion on the mail list about the release. We can provide a
template to include more clear info about opening PRs and PRs to be
cherry-picked to the released branch.
2.
Hello everyone,
I'd like to propose to release Pulsar Node.js Client Release 1.7.0
Currently, we have 14 commits [0] and there are bug fixes, security fixes and
performance improvements.
And there are open PRs [1].
If you have any important fixes or any questions, please reply to this email,
w
nodece commented on PR #69:
URL: https://github.com/apache/pulsar-test-infra/pull/69#issuecomment-1237888481
I can split this PR because this PR is complex for reviewer.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
Hi Yu,
> For these special doc PRs, can we set them to run only build (compile)
> tests and skip other code tests?
If code is updated, the build & tests shouldn't be skipped in the current
solution.
If we'd like to make the build faster and skip unnecessary tests, we would need
a more advance
Hi all,
I saw in the Pulsar Metadata handler, we retry the operation when zookeeper
throws a connection loss exception. But the operation may fail after the
retry.
For example, we update the ledgers map in memory after successfully
updating the LedgerInfo in the zookeeper. If the zookeeper update
++ Tarun
Hi Yunze,
We would love to have this.
```java
// the key is the partitioned topic name like my-topic-partition-0
void acknowledgeCumulative(Map topicToMessageId);
```
If you are busy with other things, do you mind Tarun taking this up ? Happy
to have you as a reviewer.
Regards,
Shivji
Hi Lari,
Thanks for launching this discussion. There's a lot to do to improve
contributor experience, esp for newcomers I think.
One of the pain points is obviously the CI flakyness and I believe we are
all aware of that.
Related to that, we have the pulsarbot to relaunch the tests that failed
but
Pulsar CI continues to be congested, and the build queue [1] is very long at
the moment. There are 147 build jobs in the queue and 16 jobs in progress at
the moment.
I would strongly advice everyone to use "personal CI" to mitigate the issue of
the long delay of CI feedback. You can simply open
I asked for an update on the Apache org GitHub Actions usage stats from Gavin
McDonald on the-asf slack in this thread:
https://the-asf.slack.com/archives/CBX4TSBQ8/p1662464113873539?thread_ts=1661512133.913279&cid=CBX4TSBQ8
.
I hope we get this issue resolved since it delays PR processing a lo
The Apache Infra ticket is https://issues.apache.org/jira/browse/INFRA-23633 .
-Lari
On 2022/09/06 11:36:46 Lari Hotari wrote:
> I asked for an update on the Apache org GitHub Actions usage stats from Gavin
> McDonald on the-asf slack in this thread:
> https://the-asf.slack.com/archives/CBX4TS
The Apache Pulsar team is proud to announce Apache Pulsar version 2.7.5.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subsc
We are going to need to take actions to fix our problems. See
https://issues.apache.org/jira/browse/INFRA-23633?focusedCommentId=17600749&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17600749
Jarek has done a large amount of GitHub Action work with Apache Airflo
lhotari merged PR #69:
URL: https://github.com/apache/pulsar-test-infra/pull/69
--
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.a
lhotari closed issue #59: [docbot] Cannot to label for PR correctly
URL: https://github.com/apache/pulsar-test-infra/issues/59
--
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.
T
GitHub user momo-jun added a comment to the discussion: [Design] Pulsar All
Releases Page
Cross-post the
[comment](https://github.com/apache/pulsar/issues/16938#issuecomment-1214783189)
here since the Versions page will be deprecated, and the explanation for
versioning change can be added to
Hi Xiangying
I think this is a very good optimization solution, it solves the
problem that users have a lot of aborted transactions.
Thanks!
Bo
Yubiao Feng 于2022年8月16日周二 11:33写道：
>
> Hi Xiangying
>
> >> Can the sequence id generation strategy be added to the proposal？
>
> > think it's an imple
Merged. Depending on whether [0] will be cherry picked to release
branches, I will cherry pick [1] or [2] to all active release
branches.
Thanks,
Michael
[0] https://github.com/apache/pulsar/pull/15558
[1] https://github.com/apache/pulsar/pull/17419
[2]
https://github.com/apache/pulsar/commit/b5
I see there was some recent activity on
https://github.com/apache/pulsar/issues/12944, but I don't know of any
other progress.
I won't be able to work on this in the near future, but I'll be happy
to help review any PRs related to it.
Thanks,
Michael
On Mon, Sep 5, 2022 at 8:05 AM Asaf Mesika w
18 matches
Mail list logo
