Re: [NEXT STEPS] Pulsar Release 2.10.0 Candidate 5

Close the vote 3 (+1) binding 2 (+1) non-binding 0 (-1) I will complete the following steps. Thanks, Penghui On Sat, Apr 9, 2022 at 10:48 AM Dave Fisher wrote: > Hi Peng Hui, > > Thank you for taking on the very difficult and tedious role of Release > Manager. > > Please feel free to ask for

[NEXT STEPS] Pulsar Release 2.10.0 Candidate 5

Hi Peng Hui, Thank you for taking on the very difficult and tedious role of Release Manager. Please feel free to ask for volunteers to help you complete this release. If anyone notices anything Peng Hui has missed please see if you can help! All the Best, Dave Sent from my iPhone > On Mar 26,

Re: [VOTE] Pulsar Release 2.10.0 Candidate 5

+1 (binding) Checked: * Signatures * Bin distribution: - NOTICE, README, LICENSE - Start standalone service and producer/consumer test * Src distribution: - NOTICE, README, LICENSE - Compile and unit tests - Start standalone service * Checked staging maven repository

Re: [VOTE] Pulsar Release 2.10.0 Candidate 5

+1 (binding) - Checked checksum and license - Build from source code under JDK11 - Startup standalone and run pulsar-perf to produce and consume - Startup function worker to run internal developed connectors - Run OpenMessaging to test pub-sub Thanks for Penghui's great work. Hang Nicolò Boschi

[GitHub] [pulsar-helm-chart] ckdarby commented on pull request #205: Tiered Storage config

ckdarby commented on PR #205: URL: https://github.com/apache/pulsar-helm-chart/pull/205#issuecomment-1093005135 @sijie Can you assign over to someone else to take a look? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and us

Re: [VOTE] Pulsar Release 2.10.0 Candidate 5

+1 (non binding) - Checksum and signatures - Apache Rat check passes - Compile from source w JDK11 - Build docker image from source - Run Pulsar standalone and produce-consume from CLI Nicolò Boschi Il giorno ven 8 apr 2022 alle ore 15:43 Enrico Olivelli ha scritto: > +1 (binding) > > -

Re: [VOTE] Pulsar Release 2.10.0 Candidate 5

+1 (binding) - Checked signatures, digests, Apache Rat - Run some smoke tests with Pulsar standalone from the binary tarball - Built locally and run some tests on the binaries built locally - Built the docker image locally and run some tests with the pulsar-all docker image I have checked that ou

[GitHub] [pulsar-client-node] nkurihar closed issue #14: Implement Asynchronous Processing Using C Async Function

nkurihar closed issue #14: Implement Asynchronous Processing Using C Async Function URL: https://github.com/apache/pulsar-client-node/issues/14 -- 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 sp

[GitHub] [pulsar-client-node] nkurihar commented on issue #14: Implement Asynchronous Processing Using C Async Function

nkurihar commented on issue #14: URL: https://github.com/apache/pulsar-client-node/issues/14#issuecomment-1092566482 Now AsyncWorker is replaced with async functions: https://github.com/apache/pulsar-client-node/pull/200 -- This is an automated message from the Apache Git Service. To res

Re: Re-running failed flaky builds in refactored Pulsar CI GitHub Actions workflow

With the new GitHub Actions CI workflow there are cases where you see a red mark as a failure, but there's no need to rerun failed jobs since the red failure marks are a result of failed test reports (usually from failed flaky tests). The new Pulsar CI workflow renders Junit xml test reports an