[DISCUSS] Archive Ancient (Incubating) Documents

[tison]

Hi folks,

I noticed that we write a lot of logic to handle ancient documents back to
the incubating period on the current doc site syncing and building. It
causes unnecessary maintenance burdens as well as more broken links due to
different document frameworks.

Since those ancient documents have lower visits and most importantly, we
should not make any changes to them, I propose:

1. Redirect https://pulsar.apache.org/docs/xxx-incubating/ to
https://pulsar.staged.apache.org/docs/xxx-incubating
2. Remove
https://github.com/apache/pulsar/tree/master/site2/website/versioned_docs/xxx-incubating
.
3. Remove build logic about those pages.

What do you think?

Best,
tison.

[GitHub] [pulsar-helm-chart] arnarg commented on pull request #291: Alphabetically sort list of super users

[GitBox]

arnarg commented on PR #291:
URL: 
https://github.com/apache/pulsar-helm-chart/pull/291#issuecomment-1280422676

   Doesn't seem like the failing workflows are because of my changes, right? 
@michaeljmarshall 


-- 
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

Re: [VOTE] Pulsar Release 2.10.2 Candidate 3

[Qiang Huang]

+1(non-binding)
- Checked signatures/checksums
- Built from sources using `mvn clean install -DskipTests` using JDK 17
- Run the standalone
- Validate Connectors
- Validate Pub/Sub and Java Functions
- Validate Stateful Functions

Michael Marshall  于2022年10月17日周一 12:31写道：

> +1 (binding)
>
> - Verified signatures for 48 artifacts
> - Verified checksums for 48 artifacts
> - Built from sources using `mvn clean install -DskipTests` using
> Temurin-11.0.14+9 JDK
> - Verified `mvn apache-rat:check` passes
> - Ran pulsar standalone, verified some pulsar-admin commands, verified
> perf produce/consume worked using JDK 11
>
> Thanks for running the release Haiting!
>
> - Michael
>
> On Sun, Oct 16, 2022 at 10:40 PM guo jiwei  wrote:
> >
> > +1 (binding)
> >
> > - Build from sources
> > - Checksum and signatures
> > - Run Pulsar standalone and produce/consume case
> > - Validate Pub/Sub and Java Functions
> > - Validate Connectors
> > - Validate Stateful Functions
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> >
> > On Thu, Oct 13, 2022 at 10:52 PM Enrico Olivelli 
> > wrote:
> >
> > > +1 (binding)
> > > - validated RAT, checksums and signatures
> > > - built from sources and run smoke tests on the built binaries (JDK11
> > > temurin on Mac)
> > >
> > > Thanks
> > > Enrico
> > >
> > > Il giorno gio 13 ott 2022 alle ore 13:10 houxiaoyu
> > >  ha scritto:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > - Checksum and signatures
> > > > - Build on Mac, using JDK17
> > > > - Run Pulsar standalone and produce/consume case
> > > >
> > > > Thanks,
> > > > Xiaoyu Hou
> > > >
> > > > Haiting Jiang  于2022年10月13日周四 18:52写道：
> > > >
> > > > > This is the third release candidate for Apache Pulsar, version
> 2.10.2.
> > > > >
> > > > > This release contains 252 commits by 57 contributors.
> > > > >
> https://github.com/apache/pulsar/compare/v2.10.1...v2.10.2-candidate-3
> > > > >
> > > > > CI for this release candidate
> > > > > https://github.com/Jason918/pulsar/pull/11
> > > > >
> > > > > *** 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), binaries are
> provided
> > > for
> > > > > convenience.
> > > > >
> > > > > Source and binary files:
> > > > >
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.10.2-candidate-3/
> > > > >
> > > > > SHA-512 checksums:
> > > > >
> > > > >
> > >
> c136ef4f47b3b4edfb99d8a927ba70df19c12ac28d1711825bda4ef09e543d3d473ce732996244042ec3387f0e3cafdde6c8f5a0d7d18ad24429e781e65d3328
> > > > >  ./apache-pulsar-2.10.2-bin.tar.gz
> > > > >
> > > > >
> > >
> 1fd10fbb48e734dbb95f20b0d396cb9f875a0a1c93f44b639dc730379ce93bc59ce20bfba137f28897c1e5b3351b08ca3341863c903cf2b6d3dc7108046f2f8f
> > > > >  ./apache-pulsar-2.10.2-src.tar.gz
> > > > >
> > > > > Maven staging repo:
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapachepulsar-1187/
> > > > >
> > > > > The tag to be voted upon:
> > > > > v2.10.2-candidate-3 (11b5df797b2e9cb48dfc38137f0b7ef736a8a47c)
> > > > > https://github.com/apache/pulsar/releases/tag/v2.10.2-candidate-3
> > > > >
> > > > > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > > > >
> > > > > Docker images:
> > > > >
> > > > >
> > >
> https://hub.docker.com/layers/jason918/pulsar/2.10.2/images/sha256-6a501a0dc0e05b6bbd76e0f9edd1ff7223d0447bd318332dcf9551b48e831cf9
> > > > >
> > > > >
> > >
> https://hub.docker.com/layers/jason918/pulsar-all/2.10.2/images/sha256-fd3e027771f08eb224a3a9e8874514f0f258a0356059120d3f25f151f96506c8
> > > > >
> > > > > Please download the source package, and follow the
> > > > > release-candidate-validation doc to build
> > > > > and run the Pulsar standalone service.
> > > > >
> > > > >
> > >
> https://github.com/apache/pulsar/blob/master/wiki/release/release-candidate-validation.md
> > > > >
> > > > > Thanks,
> > > > > Haiting
> > > > >
> > >
>


-- 
BR,
Qiang Huang

Re: [DISCUSS] Archive Ancient (Incubating) Documents

[Yu]

Hi tison,

Thanks for taking care of the docs!
Seems that archiving the incubating docs does not affect the existing
workflow of Pulsar doc update/maintenance.
+1 for this proposal.

Yu

On Mon, Oct 17, 2022 at 3:24 PM tison  wrote:

> Hi folks,
>
> I noticed that we write a lot of logic to handle ancient documents back to
> the incubating period on the current doc site syncing and building. It
> causes unnecessary maintenance burdens as well as more broken links due to
> different document frameworks.
>
> Since those ancient documents have lower visits and most importantly, we
> should not make any changes to them, I propose:
>
> 1. Redirect https://pulsar.apache.org/docs/xxx-incubating/ to
> https://pulsar.staged.apache.org/docs/xxx-incubating
> 2. Remove
>
> https://github.com/apache/pulsar/tree/master/site2/website/versioned_docs/xxx-incubating
> .
> 3. Remove build logic about those pages.
>
> What do you think?
>
> Best,
> tison.
>

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

[guo jiwei]

Hi
  Sorry for the late release, we need to wait for the 2 fixes on the BK
side.

  https://github.com/apache/bookkeeper/pull/3523
  https://github.com/apache/bookkeeper/pull/3528

Regards
Jiwei Guo (Tboy)


On Fri, Oct 14, 2022 at 6:02 AM Christophe Bornet 
wrote:

> The blockers mentioned by Nicolo seem to have been fixed.
> Is there still something blocking the release ?
>
> Le mer. 28 sept. 2022 à 15:36, Nicolò Boschi  a
> écrit :
>
> > I've found another release blocker about client compatibility with
> jdk8/11,
> > please review https://github.com/apache/pulsar/pull/17873
> >
> > Nicolò Boschi
> >
> >
> > Il giorno ven 16 set 2022 alle ore 10:54 Nicolò Boschi <
> > boschi1...@gmail.com>
> > ha scritto:
> >
> > > Actually Yong found the root cause of the issue, see
> > > https://lists.apache.org/thread/d9gm50kysgjcpbq448s2sy822kho6z6k -
> > > https://github.com/apache/bookkeeper/pull/3480
> > > The issue only appears if "numReadWorkerThreads" is set to zero, which
> is
> > > a non-sense config in a production environment.
> > >
> > >
> > > But I found another release blocker here:
> > > https://github.com/apache/pulsar/pull/17690
> > >
> > > After that, I think we should go forward and continue with the release.
> > > Pulsar 2.11 will contain awesome features and we already have held it
> too
> > > much based on the release schedule.
> > >
> > > Regards,
> > > Nicolò Boschi
> > >
> > >
> > > Il giorno mar 13 set 2022 alle ore 10:02 Nicolò Boschi <
> > > boschi1...@gmail.com> ha scritto:
> > >
> > >> The only blocker now should be
> > >> https://github.com/apache/pulsar/issues/17520
> > >> The description says that reverting BK to 4.15.0, the issue seems
> > >> resolved.
> > >>
> > >> If so, I think we should revert the BK upgrade and then go forward
> with
> > >> Pulsar 2.11.0.
> > >>
> > >> I know that there are some suspects of a regression in BK 4.15.0
> raised
> > >> by the Pravega team (https://github.com/apache/bookkeeper/issues/3466
> )
> > >> but we can't wait for them.
> > >> We don't know if the same issue applies to Pulsar and the time for:
> find
> > >> the issue - fix it - cut a release may be weeks or months.
> > >>
> > >>
> > >> Nicolò Boschi
> > >>
> > >>
> > >> Il giorno lun 5 set 2022 alle ore 14:03 Enrico Olivelli <
> > >> eolive...@gmail.com> ha scritto:
> > >>
> > >>> Got it
> > >>> thanks fro the update and also thanks for being so careful in
> > >>> following the issues
> > >>> and we are finding on Pulsar
> > >>>
> > >>> Il giorno lun 5 set 2022 alle ore 13:00 guo jiwei
> > >>>  ha scritto:
> > >>> >
> > >>> > Hi  dev,
> > >>> > We find two new issues[1] that block the release.
> > >>> > After the two issues are resolved, I will start the release.
> > >>> >
> > >>> > [1] : https://github.com/apache/pulsar/pull/17474
> > >>> >https://github.com/apache/bookkeeper/issues/3466
> > >>>
> > >>> This is a BookKeeper bug, so it will take much time to see it fixed
> > >>> and released in order to be
> > >>> consumed by Pulsar.
> > >>>
> > >>> The issue was reported on Pravega, that uses BK in a very different
> > way.
> > >>> I am not sure that we have to hold off this release waiting for
> > >>> feedback on that issue
> > >>>
> > >>> The 2.11 release was due to August, before PulsarSummit
> > >>>
> > >>> any other opinions from the community ?
> > >>>
> > >>>
> > >>> Enrico
> > >>>
> > >>> >
> > >>> > Regards
> > >>> > Jiwei Guo (Tboy)
> > >>> >
> > >>> >
> > >>> > On Fri, Aug 26, 2022 at 10:02 AM guo jiwei 
> > >>> wrote:
> > >>> >
> > >>> > > Hi  Anon
> > >>> > >After we cut the branch, the code freezed.
> > >>> > >
> > >>> > >
> > >>> > > Regards
> > >>> > > Jiwei Guo (Tboy)
> > >>> > >
> > >>> > >
> > >>> > > On Thu, Aug 25, 2022 at 9:45 PM Anon Hxy 
> > >>> wrote:
> > >>> > >
> > >>> > >> Hi jiwei
> > >>> > >>
> > >>> > >> Sorry for late reply.  I'd like to add PIP189 to 2.11.0, is it
> > >>> possible
> > >>> > >> now
> > >>> > >>
> > >>> > >> - PIP 189: No batching if only one message in batch.
> > >>> > >> https://github.com/apache/pulsar/pull/16605
> > >>> > >>
> > >>> > >> Thanks,
> > >>> > >> Xiaoyu Hou
> > >>> > >>
> > >>> > >> guo jiwei  于2022年8月24日周三 10:16写道：
> > >>> > >>
> > >>> > >> > Hi all,
> > >>> > >> >We have merged all the blocker patches, and I decide to
> start
> > >>> the
> > >>> > >> > release.
> > >>> > >> >The release note[1] for 2.11.0 is available for review,
> > please
> > >>> help
> > >>> > >> > review it and feel free to leave comments.
> > >>> > >> >
> > >>> > >> >
> > >>> > >> > [1] https://github.com/apache/pulsar-site/pull/167
> > >>> > >> >
> > >>> > >> >
> > >>> > >> > Regards
> > >>> > >> > Jiwei Guo (Tboy)
> > >>> > >> >
> > >>> > >> >
> > >>> > >> > On Wed, Aug 17, 2022 at 10:43 PM Enrico Olivelli <
> > >>> eolive...@gmail.com>
> > >>> > >> > wrote:
> > >>> > >> >
> > >>> > >> > > This test is blocking all the PRs and so it is blocking the
> > >>> release:
> > >>> > >> > > Error: Tests run: 9, Failures: 2, Errors: 0, 

Pulsar Flaky test report 2022-10-17 for PR builds in CI

[Nicolò Boschi]

Dear community,

Here's a report of the flaky tests in Pulsar CI during the observation
period of 2022-10-07 - 2022-10-14

https://docs.google.com/spreadsheets/d/165FHpHjs5fHccSsmQM4beeg6brn-zfUjcrXf6xAu4yQ/edit?usp=sharing



The report contains a subset of the test failures.
The flaky tests are observed from builds of merged PRs.
The GitHub Actions logs will be checked for builds where the SHA of the
head of the PR matches the SHA which got merged.
This ensures that all found exceptions are real flakes, since no changes
were made to the PR to make the tests pass later
so that the PR was merged successfully.



Top 7 flaky issues to fix:
org.apache.pulsar.client.api.SimpleProducerConsumerTest.rest 87
org.apache.pulsar.client.api.SimpleProducerConsumerTest.testConcurrentConsumerReceiveWhileReconnect
47
org.apache.pulsar.client.api.v1.V1_ProducerConsumerTest.testActiveAndInActiveConsumerEntryCacheBehavior
40
org.apache.pulsar.broker.stats.PrometheusMetricsTest.testDuplicateMetricTypeDefinitions
22
org.apache.pulsar.broker.service.persistent.SimpleProducerConsumerTestStreamingDispatcherTest.rest
14
org.apache.pulsar.metadata.ZKSessionTest.testReacquireLeadershipAfterSessionLost
13
org.apache.pulsar.broker.admin.NamespacesTest.testSplitBundleForMultiTimes
11
The main reason for all the SimpleProducerConsumerTest failures is
https://github.com/apache/pulsar/pull/17887 and this is a possible fix:
https://github.com/apache/pulsar/pull/18068

Markdown formatted summary reports for each test class can be accessed at
https://github.com/nicoloboschi/pulsar-flakes/tree/master/2022-10-07-to-2022-10-14

More flaky test issues:
https://github.com/apache/pulsar/issues?q=flaky
+sort%3Aupdated-desc+is%3Aopen+is:issue

We need more help in addressing the flaky tests. Please join the efforts
so that we can get CI to a more stable state.

To coordinate the work,
1) please search for an existing issues or search for all flaky issues with
"flaky" or the test class name (without package) in the search:
https://github.com/apache/pulsar/issues?q=is%3Aopen+flaky+sort%3Aupdated-desc
2) If there isn't an issue for a particular flaky test failure that you'd
like to fix, please create an issue using the "Flaky test" template at
https://github.com/apache/pulsar/issues/new/choose
3) Please comment on the issue that you are working on.

We have a few active contributors working on the flaky tests, thanks for
the contributions.

I'm looking forward to more contributors joining the efforts. Please join
the #testing channel on Slack if you'd like to ask questions and tips about
reproducing flaky tests locally and how to fix them.
Sharing stories about fixing flaky tests is also helpful for sharing the
knowledge about how flaky tests can be fixed. That's also a valuable way to
contribute.
Some flaky tests might be actual real production code bugs. Fixing
the flaky test might result in fixing a real production code bug.

More contributions are welcome! Please keep up the good work!

(Also thanks to Lari for all the work done to have these clean reports)

Thanks,
Nicolò Boschi

[GitHub] [pulsar-dotpulsar] amareshmad commented on issue #114: When i run test console app consumer is creating and when i integrate same to actual product consumer is not creating and going to Fault

[GitBox]

amareshmad commented on issue #114:
URL: 
https://github.com/apache/pulsar-dotpulsar/issues/114#issuecomment-1280725410

   Connection established from product code 
   
   Consumer code:
 await using var client = PulsarClient.Builder()
.Authentication(new 
AuthenticationBasic(username, password))
.ServiceUrl(sURl)

.ExceptionHandler(pException.OnException)

.VerifyCertificateAuthority(false)

.TrustedCertificateAuthority(new 
System.Security.Cryptography.X509Certificates.X509Certificate2())
.Build();
   
   log.Info($"creating Consumer...");
   await using var consumer = 
client.NewConsumer(Schema.ByteArray)
.Topic(myTopic) 
   

.SubscriptionName(subscriptionName)

.SubscriptionType(SubscriptionType.Shared)

.StateChangedHandler(DESPulsarQueue.Monitor)
.Create();
   
   
   producer code:   log.Info($"build producer client");
   ExceptionHandler pException = new ExceptionHandler();
   
   await using var client = PulsarClient.Builder()
.Authentication(new 
AuthenticationBasic(username, password))
.ServiceUrl(sURl)

.ExceptionHandler(pException.OnException)

.VerifyCertificateAuthority(false)

.TrustedCertificateAuthority(new 
System.Security.Cryptography.X509Certificates.X509Certificate2())
.Build();
   
   log.Info($"creating producer...");
   await using var producer = client.NewProducer(Schema.String)
.Topic(myTopic)

.StateChangedHandler(Monitor)
.Create();
   Source helped to setting up TLS layers: 
https://support.avigilon.com/s/article/How-to-Check-if-TLS-1-2-is-Enabled?language=en_US
   


-- 
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 closed issue #114: When i run test console app consumer is creating and when i integrate same to actual product consumer is not creating and going to Faulted

[GitBox]

blankensteiner closed issue #114: When i run test console app consumer is 
creating and when i integrate same to actual product consumer is not creating 
and going to Faulted state
URL: https://github.com/apache/pulsar-dotpulsar/issues/114


-- 
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 commented on issue #114: When i run test console app consumer is creating and when i integrate same to actual product consumer is not creating and going to F

[GitBox]

blankensteiner commented on issue #114:
URL: 
https://github.com/apache/pulsar-dotpulsar/issues/114#issuecomment-1280794621

   Glad to hear it. TLS can be tricky :-)


-- 
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] michaeljmarshall commented on pull request #291: Alphabetically sort list of super users

[GitBox]

michaeljmarshall commented on PR #291:
URL: 
https://github.com/apache/pulsar-helm-chart/pull/291#issuecomment-1280978613

   No, these might just be flaky workflows. I triggered the failed jobs to run 
again.


-- 
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] michaeljmarshall opened a new pull request, #115: Only send notifications to commits@ ML

[GitBox]

michaeljmarshall opened a new pull request, #115:
URL: https://github.com/apache/pulsar-dotpulsar/pull/115

   This PR modifies the Apache mailing list notifications so that commits, 
issues, and pull request notifications are sent to the 
comm...@pulsar.apache.org mailing list. If you would like these notifications, 
please to subscribe to the commits mailing list or use the GitHub "watch" 
feature.
   
   Mailing list discussion for this change: 
https://lists.apache.org/thread/j6y57kr4180xblh7voyrjw47blgmghwt


-- 
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] michaeljmarshall opened a new pull request, #302: Only send notifications to commits@ ML

[GitBox]

michaeljmarshall opened a new pull request, #302:
URL: https://github.com/apache/pulsar-helm-chart/pull/302

   This PR modifies the Apache mailing list notifications so that commits, 
issues, and pull request notifications are sent to the 
comm...@pulsar.apache.org mailing list. If you would like these notifications, 
please to subscribe to the commits mailing list or use the GitHub "watch" 
feature.
   
   Mailing list discussion for this change: 
https://lists.apache.org/thread/j6y57kr4180xblh7voyrjw47blgmghwt
   


-- 
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-client-node] michaeljmarshall opened a new pull request, #236: Only send notifications to commits@ ML

[GitBox]

michaeljmarshall opened a new pull request, #236:
URL: https://github.com/apache/pulsar-client-node/pull/236

   This PR modifies the Apache mailing list notifications so that commits, 
issues, and pull request notifications are sent to the 
comm...@pulsar.apache.org mailing list. If you would like these notifications, 
please to subscribe to the commits mailing list or use the GitHub "watch" 
feature.
   
   Mailing list discussion for this change: 
https://lists.apache.org/thread/j6y57kr4180xblh7voyrjw47blgmghwt


-- 
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-client-node] michaeljmarshall merged pull request #236: Only send notifications to commits@ ML

[GitBox]

michaeljmarshall merged PR #236:
URL: https://github.com/apache/pulsar-client-node/pull/236


-- 
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] michaeljmarshall merged pull request #302: Only send notifications to commits@ ML

[GitBox]

michaeljmarshall merged PR #302:
URL: https://github.com/apache/pulsar-helm-chart/pull/302


-- 
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] michaeljmarshall merged pull request #115: Only send notifications to commits@ ML

[GitBox]

michaeljmarshall merged PR #115:
URL: https://github.com/apache/pulsar-dotpulsar/pull/115


-- 
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

Re: [DISCUSS] Decrease GitHub email notifications from apache/pulsar-* repos to this ML

[Michael Marshall]

I merged the following PRs as a result of this discussion:

https://github.com/apache/pulsar-client-node/pull/236
https://github.com/apache/pulsar-client-go/pull/861
https://github.com/apache/pulsar-helm-chart/pull/302
https://github.com/apache/pulsar-dotpulsar/pull/115

If you would like to get granular notifications for any Apache Pulsar
git repositories, please subscribe to the commits mailing list or use
an available GitHub feature.

Thanks,
Michael

On Wed, Oct 12, 2022 at 8:17 AM Devin Bost  wrote:
>
> +1
>
> On Wed, Oct 12, 2022, 7:49 AM Xiangying Meng  wrote:
>
> > +1
> >
> > Thanks,
> > Xiangying
> >
> > On Wed, Oct 12, 2022 at 7:11 PM Haiting Jiang 
> > wrote:
> >
> > > +1
> > >
> > > Thanks,
> > > Haiting
> > >
> > > On Wed, Oct 12, 2022 at 5:46 PM houxiaoyu  wrote:
> > > >
> > > > +1
> > > > Very useful.
> > > >
> > > > Michael Marshall  于2022年10月12日周三 12:52写道：
> > > >
> > > > > Hi All,
> > > > >
> > > > > I had a brief discussion with Matteo about mailing list notifications
> > > > > for our apache/pulsar-* repos in this PR
> > > > > https://github.com/apache/pulsar-client-cpp/pull/42. Please see it
> > for
> > > > > additional context.
> > > > >
> > > > > The outcome is a proposal to make all of our GitHub repos send their
> > > > > notifications to commits@ instead of dev@. Contributors will be able
> > > > > to subscribe to updates by using the GitHub "watch" feature.
> > > > >
> > > > > I created a sample PR here:
> > > > > https://github.com/apache/pulsar-client-go/pull/861.
> > > > >
> > > > > If there are no major objections, I plan to move forward with the
> > rest
> > > > > of our repos later this week.
> > > > >
> > > > > Thanks,
> > > > > Michael
> > > > >
> > >
> >

Re: [Vote] PIP-192 New Pulsar Broker Load Balancer

[Heesung Sohn]

Hi Enrico,

We internally did PoC work and presented the demo(local bundle state
channel test) in the Apache Con 2022 NA.

We just started raising PRs for this project, and we will be tagging the PR
titles with [pip-192].

Thank you,
Heesung



On Wed, Oct 12, 2022 at 11:33 PM Enrico Olivelli 
wrote:

> +1 (binding)
>
> What's the status of this PIP ?
>
> Enrico
>
> Il giorno gio 25 ago 2022 alle ore 05:04 Hang Chen
>  ha scritto:
> >
> > +1 (binding)
> >
> > Awesome job!
> >
> > Thanks,
> > Hang
> >
> > Heesung Sohn  于2022年8月24日周三
> 05:29写道：
> > >
> > > Hi, Pulsar dev community,
> > >
> > > This vote has been open for 23 days, and we are closing this vote
> today as
> > > this PIP received three binding +1s.
> > >
> > > We are moving forward and starting implementation -- there will be a
> series
> > > of PRs and sub-PIPs(if further design discussions are required).
> > >
> > > Thank you,
> > > Heesung
> > >
> > > On Tue, Aug 9, 2022 at 4:56 AM guo jiwei  wrote:
> > >
> > > > +1
> > > >
> > > > Regards
> > > > Jiwei Guo (Tboy)
> > > >
> > > >
> > > > On Tue, Aug 9, 2022 at 3:12 PM Qiang Huang <
> qiang.huang1...@gmail.com>
> > > > wrote:
> > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > Kai Wang  于2022年8月5日周五 10:18写道：
> > > > >
> > > > > > +1 (non-binding)
> > > > > >
> > > > > > Thanks,
> > > > > > Kai
> > > > > >
> > > > > > Heesung Sohn  于2022年8月2日周二
> > > > > 08:50写道：
> > > > > >
> > > > > > > Dear Pulsar Community,
> > > > > > >
> > > > > > > Please review and vote on this PIP.
> > > > > > >
> > > > > > > PIP link: https://github.com/apache/pulsar/issues/16691
> > > > > > >
> > > > > > > Thank you,
> > > > > > > -Heesung
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > BR,
> > > > > Qiang Huang
> > > > >
> > > >
>

Re: [VOTE] Pulsar Release 2.10.2 Candidate 3

[Haiting Jiang]

Thank you all.
Closing this vote with 3 binding +1s and 2 non-binding +1s.

Thanks,
Haiting

On Mon, Oct 17, 2022 at 3:57 PM Qiang Huang  wrote:
>
> +1(non-binding)
> - Checked signatures/checksums
> - Built from sources using `mvn clean install -DskipTests` using JDK 17
> - Run the standalone
> - Validate Connectors
> - Validate Pub/Sub and Java Functions
> - Validate Stateful Functions
>
> Michael Marshall  于2022年10月17日周一 12:31写道：
>
> > +1 (binding)
> >
> > - Verified signatures for 48 artifacts
> > - Verified checksums for 48 artifacts
> > - Built from sources using `mvn clean install -DskipTests` using
> > Temurin-11.0.14+9 JDK
> > - Verified `mvn apache-rat:check` passes
> > - Ran pulsar standalone, verified some pulsar-admin commands, verified
> > perf produce/consume worked using JDK 11
> >
> > Thanks for running the release Haiting!
> >
> > - Michael
> >
> > On Sun, Oct 16, 2022 at 10:40 PM guo jiwei  wrote:
> > >
> > > +1 (binding)
> > >
> > > - Build from sources
> > > - Checksum and signatures
> > > - Run Pulsar standalone and produce/consume case
> > > - Validate Pub/Sub and Java Functions
> > > - Validate Connectors
> > > - Validate Stateful Functions
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> > >
> > >
> > > On Thu, Oct 13, 2022 at 10:52 PM Enrico Olivelli 
> > > wrote:
> > >
> > > > +1 (binding)
> > > > - validated RAT, checksums and signatures
> > > > - built from sources and run smoke tests on the built binaries (JDK11
> > > > temurin on Mac)
> > > >
> > > > Thanks
> > > > Enrico
> > > >
> > > > Il giorno gio 13 ott 2022 alle ore 13:10 houxiaoyu
> > > >  ha scritto:
> > > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > - Checksum and signatures
> > > > > - Build on Mac, using JDK17
> > > > > - Run Pulsar standalone and produce/consume case
> > > > >
> > > > > Thanks,
> > > > > Xiaoyu Hou
> > > > >
> > > > > Haiting Jiang  于2022年10月13日周四 18:52写道：
> > > > >
> > > > > > This is the third release candidate for Apache Pulsar, version
> > 2.10.2.
> > > > > >
> > > > > > This release contains 252 commits by 57 contributors.
> > > > > >
> > https://github.com/apache/pulsar/compare/v2.10.1...v2.10.2-candidate-3
> > > > > >
> > > > > > CI for this release candidate
> > > > > > https://github.com/Jason918/pulsar/pull/11
> > > > > >
> > > > > > *** 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), binaries are
> > provided
> > > > for
> > > > > > convenience.
> > > > > >
> > > > > > Source and binary files:
> > > > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.10.2-candidate-3/
> > > > > >
> > > > > > SHA-512 checksums:
> > > > > >
> > > > > >
> > > >
> > c136ef4f47b3b4edfb99d8a927ba70df19c12ac28d1711825bda4ef09e543d3d473ce732996244042ec3387f0e3cafdde6c8f5a0d7d18ad24429e781e65d3328
> > > > > >  ./apache-pulsar-2.10.2-bin.tar.gz
> > > > > >
> > > > > >
> > > >
> > 1fd10fbb48e734dbb95f20b0d396cb9f875a0a1c93f44b639dc730379ce93bc59ce20bfba137f28897c1e5b3351b08ca3341863c903cf2b6d3dc7108046f2f8f
> > > > > >  ./apache-pulsar-2.10.2-src.tar.gz
> > > > > >
> > > > > > Maven staging repo:
> > > > > >
> > > >
> > https://repository.apache.org/content/repositories/orgapachepulsar-1187/
> > > > > >
> > > > > > The tag to be voted upon:
> > > > > > v2.10.2-candidate-3 (11b5df797b2e9cb48dfc38137f0b7ef736a8a47c)
> > > > > > https://github.com/apache/pulsar/releases/tag/v2.10.2-candidate-3
> > > > > >
> > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release:
> > > > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> > > > > >
> > > > > > Docker images:
> > > > > >
> > > > > >
> > > >
> > https://hub.docker.com/layers/jason918/pulsar/2.10.2/images/sha256-6a501a0dc0e05b6bbd76e0f9edd1ff7223d0447bd318332dcf9551b48e831cf9
> > > > > >
> > > > > >
> > > >
> > https://hub.docker.com/layers/jason918/pulsar-all/2.10.2/images/sha256-fd3e027771f08eb224a3a9e8874514f0f258a0356059120d3f25f151f96506c8
> > > > > >
> > > > > > Please download the source package, and follow the
> > > > > > release-candidate-validation doc to build
> > > > > > and run the Pulsar standalone service.
> > > > > >
> > > > > >
> > > >
> > https://github.com/apache/pulsar/blob/master/wiki/release/release-candidate-validation.md
> > > > > >
> > > > > > Thanks,
> > > > > > Haiting
> > > > > >
> > > >
> >
>
>
> --
> BR,
> Qiang Huang