[GitHub] [pulsar-site] Anonymitaet commented on pull request #52: Updated sidebar label tags

Anonymitaet commented on PR #52: URL: https://github.com/apache/pulsar-site/pull/52#issuecomment-1106075090 @DaveDuggins why modify the sidebar and make them look the same? https://user-images.githubusercontent.com/50226895/164621294-9c67052e-7afd-4eca-849b-4a673525aff3.png";> -- Th

Re: Enable GitHub Discussions?

Thanks all! I understand that we need to follow the Apache way (If it didn’t happen on the mailing list, it didn’t happen) to *make final decisions*, but we can find a better place to *discuss issues and reuse information effectively* [1]. # Current issues We have a lot of work in vari

Re: [DISCUSS] [PIP-154] Max active transaction limitation for transaction coordinator

Hi Haiting, We have the active txn count metrics, but don't have the "active transaction usage percent", I think we can use active txn count to implement the monitor and alert. PR : https://github.com/apache/pulsar/pull/10651 Thanks, Bo Haiting Jiang 于2022年4月19日周二 11:38写道： > > Hi Bo, > > Do we

Re: [VOTE] [PIP-150] Support read the message of startMessageId position on the broker side

+1 Thanks, Hang Zixuan Liu 于2022年4月11日周一 18:30写道： > > This way is right. > > PengHui Li 于2022年4月11日周一 09:12写道： > > > > regarding the compatibility, should we check the protocol version at the > > client side? > > The old version version doesn't support `start_message_id_inclusive` which > > mea

[GitHub] [pulsar-site] Paul-TT opened a new pull request, #56: ecosystem updates

Paul-TT opened a new pull request, #56: URL: https://github.com/apache/pulsar-site/pull/56 - Adding newest blog post - Update Ecosystem categories - Change home page h1 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

Re: Enable GitHub Discussions?

I asked Infra. GitHub Discussions are not synchronized into ASF Infrastructure's GitBox. That means that there is not ability to change the notification scheme to send to a mailing list. Technically we can go down this path only if it is possible to set a notification within GitHub. You would n

[GitHub] [pulsar-client-node] Matt-Esch commented on pull request #209: cleanup warnings

Matt-Esch commented on PR #209: URL: https://github.com/apache/pulsar-client-node/pull/209#issuecomment-1105325359 this was already addressed, closing -- 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 g

[GitHub] [pulsar-client-node] Matt-Esch closed pull request #209: cleanup warnings

Matt-Esch closed pull request #209: cleanup warnings URL: https://github.com/apache/pulsar-client-node/pull/209 -- 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,

[GitHub] [pulsar-client-node] Matt-Esch opened a new pull request, #209: cleanup warnings

Matt-Esch opened a new pull request, #209: URL: https://github.com/apache/pulsar-client-node/pull/209 Installing on OSX I noticed a few warnings that should be addressed - node-pre-gyp updated for security warnings - several compiler warnings addressed -- This is an automated

Re: Enable GitHub Discussions?

If we can bring GitHub Discussions threads to dev@ or users@ (by categorized), it won't affect workflow based on mailing list. Basically, you can discuss via GitHub Discussion by emails. Best, tison. Dianjin Wang 于2022年4月21日周四 21:43写道： > Agreed with @Enrico. If enabling the GitHub discussions

Re: Enable GitHub Discussions?

Agreed with @Enrico. If enabling the GitHub discussions, it's confusing for community members to recognize issues or discussions. If too many platforms, it's also hard for people to be focused. Best, Dianjin Wang On Thu, Apr 21, 2022 at 8:49 PM Enrico Olivelli wrote: > I believe that we should

[DISCUSS] PIP-157: Bucketing topic metadata to allow more topics per namespace

Hi everyone, I've just created a proposal that will help scaling up the number of topics per namespace. It's available at https://github.com/apache/pulsar/issues/15254 and is copied below. Let me know what you think. Thanks, Andras Motivation Pulsar is able to manage millions of topics but the

Re: Enable GitHub Discussions?

I believe that we should stick as much as possible to the mailing list, this is the common way of running the community in the ASF. We already have a Slack space that is hard to follow. Enrico Il giorno gio 21 apr 2022 alle ore 14:47 tison ha scritto: > > You can ask for ASF INFRA to see whethe

Re: Enable GitHub Discussions?

You can ask for ASF INFRA to see whether there is a way to bring all activities of GitHub Discussion to a mailing list. Just like development activities to commits@. Best, tison. Niclas Hedhman 于2022年4月21日周四 20:16写道： > > If/when GitHub disappears, will the community suffer from missing > infor

Re: [VOTE] PIP-155: Drop support for Python2

+1 (non-binding) -- Thanks Xiaolong Ran Jiuming Tao 于2022年4月21日周四 19:00写道： > +1 > Thanks, > Tao Jiuming > > > 2022年4月20日 下午8:42，Matteo Merli 写道： > > > > https://github.com/apache/pulsar/issues/15185 > > > > ## Motivation > > > > Python 2.x has been deprecated for many years now and it was > >

Re: [VOTE] [PIP-152] Support subscription level dispatch rate limiter setting.

+1 Thanks Xiaolong Ran Zike Yang 于2022年4月20日周三 09:41写道： > +1 > > Thanks, > Zike > > On Wed, Apr 20, 2022 at 9:20 AM Dezhi Liu > wrote: > > > > +1 > > > > Dezhi Liu >

Re: [ANNOUNCE] New Committer: Zike Yang

Congratulations zike -- Thanks Xiaolong Ran guo jiwei 于2022年4月19日周二 09:44写道： > Congrats > > > Regards > Jiwei Guo (Tboy) > > > On Mon, Apr 18, 2022 at 5:37 PM ZhangJian He wrote: > > > Congratulations > > > > Thanks > > ZhangJian He > > > > Ran Gao 于2022年4月18日周一 13:33写道： > > > > > Hi, zike, c

Re: [VOTE] PIP-155: Drop support for Python2

+1 Thanks, Tao Jiuming > 2022年4月20日 下午8:42，Matteo Merli 写道： > > https://github.com/apache/pulsar/issues/15185 > > ## Motivation > > Python 2.x has been deprecated for many years now and it was > officially end-of-lifed 2.5 years ago > (https://www.python.org/doc/sunset-python-2/). > > We have

Re: PIP-156: Build and Run Pulsar Server on Java 17

+1 Thanks, Tao Jiuming > 2022年4月19日 上午2:25，Heesung Sohn 写道： > > Dear Pulsar dev community, > > My name is Heesung Sohn, and I would like to open a discussion here > about PIP-156: > Build and Run Pulsar Server on Java 17 > . > > > @Nicolò Boschi,

[GitHub] [pulsar-test-infra] eolivelli merged pull request #33: [pulsarbot] Handle bug in "/pulsarbot rerun-failure-checks" that reruns obsolete jobs

eolivelli merged PR #33: URL: https://github.com/apache/pulsar-test-infra/pull/33 -- 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

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

I have made a fix to the problem described below. Please review https://github.com/apache/pulsar-test-infra/pull/33 . After this change is merged, closing and reopening PRs could be used to pick up most recent change from the master branch and "/pulsarbot rerun-failure-checks" will be able to re

Enable GitHub Discussions?

Hi Pulsarers, Recently, we've found that many open source communities use GitHub Discussions to facilitate effective communication, such as users can ask questions, share ideas, and build connections with each other easily [1]. GitHub Discussions is designed to: - Provide centralized community s

[GitHub] [pulsar-test-infra] lhotari commented on pull request #28: fix: fix get failured checks

lhotari commented on PR #28: URL: https://github.com/apache/pulsar-test-infra/pull/28#issuecomment-1104908056 I have fixed the rerunning in cases where the PR's head sha doesn't change (for example closing and reopening the PR to trigger a new build): https://github.com/apache/pulsar-test-i

[GitHub] [pulsar-test-infra] lhotari opened a new pull request, #33: [pulsarbot] Handle bug in "/pulsarbot rerun-failure-checks" that reruns obsolete jobs

lhotari opened a new pull request, #33: URL: https://github.com/apache/pulsar-test-infra/pull/33 ### Motivation Currently "/pulsarbot rerun-failure-checks" might rerun obsolete jobs. The jobs to rerun are searched by the PR's head commit SHA. If the PR is closed and re-opened or the

Re: Categorize Pulsar Plugins

OK, thanks for your explanation, Chris. FYI: I've organized all components around Pulsar here: https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=1261350388 On Wed, Apr 20, 2022 at 11:48 PM Chris Bartholomew < chris.bartholo...@kesque.com> wrote: > Hi A