fabian4 opened a new issue #445:
URL: https://github.com/apache/pulsar-manager/issues/445
Using [Casdoor](https://github.com/casdoor/casdoor) for auth over in-house
authentication method.
Features:
1. Front-end and back-end separate architecture, Casdoor supports high
concurrency
Congratulations
On Wed, Feb 16, 2022 at 11:39 AM Yu wrote:
> Hi Lili,
>
> Congrats! Well deserved! You've made a lot of great changes to the Pulsar
> website!
>
> On Tue, Feb 15, 2022 at 5:56 PM ZhangJian He wrote:
>
> > Congratulations
> >
> > Thanks
> > ZhangJian He
> >
> > Huanli Meng 于202
This is the second release candidate for Apache Pulsar, version 2.8.3.
It fixes the following issues:
https://github.com/apache/pulsar/compare/v2.8.2...v2.8.3-candidate-2
*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***
Note that we are votin
Hi Yu,
I support keeping the docs repo in the main repo. I find it helpful to
be able to search through the docs along with the code, and as you
mention, it makes it easier for developers to contribute documentation
as a part of PRs that introduce new features.
My one concern is the `pulsar-site`
Hi Lili,
Congrats! Well deserved! You've made a lot of great changes to the Pulsar
website!
On Tue, Feb 15, 2022 at 5:56 PM ZhangJian He wrote:
> Congratulations
>
> Thanks
> ZhangJian He
>
> Huanli Meng 于2022年2月15日周二 17:03写道：
>
> > Congratulations Li.
> >
> > BR// Huanli
> >
> > > On Feb 15,
Hi everyone,
Please review and vote on the release candidate #1 for the version
0.8.0, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
This is the first release candidate for Apache Pulsar Go client, version 0.8.0.
It fixes the followi
Yes, all necessary PRs are cherry-picked to branch-2.9, and the test pass,
refer to https://github.com/apache/pulsar/commits/branch-2.9, I'm cutting the
new RC from the current branch-2.9.
On 2022/02/15 14:57:25 Enrico Olivelli wrote:
> Ran,
> Are we cutting the new RC from the current branch-2.
Hi Pulsarers,
Since there is no discussion and objection, we'll keep the doc repo stay in
the pulsar repo and continue to move forward with PIP 87.
Hi Enrico, do you mean the price of LucidChart? Here it is:
[image: image.png]
https://lucid.app/pricing/lucidchart?gclid=EAIaIQobChMI3oGGyKGD9gIVnpFmAh1_gwr1EAAYASAAEgI7q_D_BwE#/pricing?utm_source=google&utm_medium=cpc&utm_campaign=_chart_en_tier3_mixed_search_brand_bmm_&km_CPC_CampaignId=148456
Hi Lari,
> Thanks for replying, Penghui. The problem is that there is no rationale
nor description in that PR, https://github.com/apache/pulsar/pull/13666 .
The only sentence there is "Avoid call sync method in async rest API for
delete subscription".
For https://github.com/apache/pulsar/pull/13
> Just a friendly reminder that we are an open source project and other
community members who may have different internal testing may find better
fixes.
Sorry, dave. I know we are an open source project.
We found a problem in our internal test, we need to confirm it is not
the test issue right?
D
> On Feb 15, 2022, at 3:59 PM, PengHui Li wrote:
>
>> I wonder if we should be more willing to share suspicions on the
> mailing list when releases are actively being prepared. I would
> have appreciated the notice, and I could have possibly helped
> confirm the issue. On the other hand, I res
> I wonder if we should be more willing to share suspicions on the
mailing list when releases are actively being prepared. I would
have appreciated the notice, and I could have possibly helped
confirm the issue. On the other hand, I respect that it is hard to
know when to share a theory and when to
ddieruf closed issue #99:
URL: https://github.com/apache/pulsar-dotpulsar/issues/99
--
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..
ddieruf commented on issue #99:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/99#issuecomment-1039344616
--
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 unsubs
blankensteiner commented on issue #99:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/99#issuecomment-1039534679
Ah, yes it's here:
https://github.com/apache/pulsar/blob/master/pulsar-common/src/main/proto/PulsarApi.proto
and we generated the cs-file based on version 281163b of th
ddieruf closed issue #99:
URL: https://github.com/apache/pulsar-dotpulsar/issues/99
--
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..
ddieruf commented on issue #99:
URL:
https://github.com/apache/pulsar-dotpulsar/issues/99#issuecomment-1040563851
Yes, thank you. I have to shift my thinking. Because this client is not in
parity with the platform, claiming a certain version's compatibility is not
useful. Also adding in b
Are we keeping all of the git history in that transition? If we plan
on dropping history, is that something we can do now?
Thanks,
Michael
On Tue, Feb 15, 2022 at 11:19 AM Dave Fisher wrote:
>
> Before the asf-site branch can deleted the people working on the website need
> to finish the transi
Closing the vote with one -1 from Penghui.
> We just confirmed yesterday that this is a breaking change,
> I was just suspicious before, so do not share the information
> to avoid confusing reviewers. For now, we confirmed it
I wonder if we should be more willing to share suspicions on the
mailin
Before the asf-site branch can deleted the people working on the website need
to finish the transition of https://github.com/apache/pulsar-site to build the
main site and not a staging site.
All the best,
Dave
> On Feb 15, 2022, at 8:55 AM, Michael Marshall wrote:
>
> Now that https://github.
Now that https://github.com/apache/pulsar/pull/14226 is merged, our
current release branches are correctly protected from force pushes.
Importantly, the `asf-site` branch is no longer protected. That branch
is responsible for quite a bit of data in our git repo. Anecdotally,
when I tried to clone
While it may be possible to create a function with a normal user, it
would be better to be able to specify the function's authentication
credentials.
> You don't need tenant admin access to create functions, you just need
> to give "functions" access to a normal user:
This user may not be an admi
Ran,
Are we cutting the new RC from the current branch-2.9?
Enrico
Il Mar 15 Feb 2022, 14:57 PengHui Li ha scritto:
> Hi Ran,
>
> I think all the PRs that block the 2.9.2 release are merged.
> Could you please help cherry-pick the PRs and start a new RC?
>
> Thanks,
> Penghui
>
> On Mon, Feb 14
On 2022/02/15 14:13:59 PengHui Li wrote:
> The rationale for these changes, I think it starts from this PR
> https://github.com/apache/pulsar/pull/13666
> This is the only one example, we have seen the same issue again and again.
> After #13666 get merged,
> The contributors found there are many pl
> Was this about the issue which this PR
https://github.com/apache/pulsar/pull/14283 resolved (since it is merged)?
I have the feeling that some past problems haven't been analyzed properly
before deciding on the solution. There seems to be an understanding that
switching from synchronous programm
Thanks for pointing that out. I'll re-run the failed builds for commit
https://github.com/apache/pulsar/commit/ed40840a65c413202c0aab6b9b1a29ed370f6fb7
.
-Lari
On Tue, Feb 15, 2022 at 3:54 PM PengHui Li wrote:
> Hi Lari
>
> The PR you shared https://github.com/apache/pulsar/pull/14240 does not
Hi Ran,
I think all the PRs that block the 2.9.2 release are merged.
Could you please help cherry-pick the PRs and start a new RC?
Thanks,
Penghui
On Mon, Feb 14, 2022 at 8:25 PM PengHui Li wrote:
> Hi Lari,
>
> We have another issue that needs to confirm if it will introduce break
> changes i
Hi Lari
The PR you shared https://github.com/apache/pulsar/pull/14240 does not run
any tests.
All the tests were completed in 1 min, please check.
Thanks,
Penghui
On Tue, Feb 15, 2022 at 7:23 PM Lari Hotari wrote:
> The tests passed for the a PR based on revision a27e0853bda in branch-2.7
>
Yu,
Il Mar 15 Feb 2022, 13:12 Yu ha scritto:
> Bumping up this thread, any thoughts? Thanks
>
> On Fri, Jan 28, 2022 at 1:00 AM Yu wrote:
>
> > Hi Pulsarers,
> >
> >
> > As you may notice, the images in Pulsar documentation are in inconsistent
> > styles, which affect user experience. This issu
Bumping up this thread, any thoughts? Thanks
On Fri, Jan 28, 2022 at 1:00 AM Yu wrote:
> Hi Pulsarers,
>
>
> As you may notice, the images in Pulsar documentation are in inconsistent
> styles, which affect user experience. This issue may be caused by:
>
> 1) Pulsar community does not have design
The tests passed for the a PR based on revision a27e0853bda in branch-2.7 in
this PR that I made to run the tests:
https://github.com/apache/pulsar/pull/14240 . rev a27e0853bda is the last
commit before the 2.7.5 release commit in branch-2.7 .
I'll count your vote as +1 since all tests have pas
tuteng opened a new pull request #194:
URL: https://github.com/apache/pulsar-client-node/pull/194
* Support for specified architectures
--
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
Thanks for the detailed reply, Penghui.
> And, for the new metadata API, we found an issue that will introduce the
> cache inconsistent issue,
> we are working on a fix, it should be a release blocker, otherwise,
> 2.10 will not able to use.
Was this about the issue which this PR
https://github.
czhfe opened a new issue #228:
URL: https://github.com/apache/pulsar-helm-chart/issues/228
broker's restartPodsOnConfigMapChange set to true, helm upgrade after broker
exception
 has invited Li Li
> > https://github.com/urfreespace to become a commit
Congratulations Li.
BR// Huanli
> On Feb 15, 2022, at 3:06 PM, PengHui Li wrote:
>
> The Apache Pulsar Project Management Committee (PMC) has invited Li Li
> https://github.com/urfreespace to become a committer and we are pleased to
> announce that he has accepted.
>
> Li Li has done a great c
37 matches
Mail list logo
