Re: Name of sequence node is not unique

Hi Enrico, Thanks for the great suggestions. On Fri, Jun 16, 2023 at 3:43 AM Enrico Olivelli wrote: > Li, > > Il giorno ven 16 giu 2023 alle ore 11:43 Li Wang ha > scritto: > > > > Thanks for the comments and inputs, Ted, Josef and Kezhu. The discussions > > are great. > > > > > The invariant

[jira] [Created] (ZOOKEEPER-4706) Use 64 bits counter to ensure monotonically increasing and uniqueness of sequence node name

Li Wang created ZOOKEEPER-4706: -- Summary: Use 64 bits counter to ensure monotonically increasing and uniqueness of sequence node name Key: ZOOKEEPER-4706 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4706

Re: ZooKeeper release 3.9.0

Thanks Andor & Enrico! We will keep verifying and ensuring the quality of the TLA+ specifications for ZooKeeper. Best regards, Sirius > 2023年6月17日 03:59，Andor Molnar 写道： > > Submitted. > > (was a great opportunity to verify the new Merge button restrictions) > > Thanks, > Andor > > >

Re: zk-merge-pr.py

... and this is the related API endpoint https://docs.github.com/en/rest/pulls/pulls?apiVersion=2022-11-28#merge-a-pull-request Best, tison. tison 于2023年6月17日周六 04:09写道： > For issuing GitHub API calls, I use https://github.com/yanyongyu/githubkit > that generated from GitHub API definitions

Re: zk-merge-pr.py

For issuing GitHub API calls, I use https://github.com/yanyongyu/githubkit that generated from GitHub API definitions and the maintainer is active. Best, tison. Andor Molnar 于2023年6月17日周六 04:06写道： > Hi all, > > The greatest advantage of our merge script is the ability of > backporting to

zk-merge-pr.py

Hi all, The greatest advantage of our merge script is the ability of backporting to other branches. The greatest disadvantage of our merge script is it closes the pull request (red color) instead of "merging" (purple color). We could replace the current pure git approach of merging the main

Re: ZooKeeper release 3.9.0

Submitted. (was a great opportunity to verify the new Merge button restrictions) Thanks, Andor On Fri, 2023-06-16 at 16:27 +0200, Andor Molnar wrote: > Looks like Michael and Flavio have already reviewed and approved it, > so > let's merge it then. > > Andor > > > > On Fri, 2023-06-16 at

Re: ZooKeeper release 3.9.0

Looks like Michael and Flavio have already reviewed and approved it, so let's merge it then. Andor On Fri, 2023-06-16 at 16:12 +0200, Enrico Olivelli wrote: > Sirius, > > Il giorno ven 16 giu 2023 alle ore 15:09 Yang Sirius > ha scritto: > > Hi Andor, > > > > I am writing to inquire about

Re: Current master branch is broker

Thank you Andor for managing this! Best, Kezhu Wang On Fri, Jun 16, 2023 at 10:01 PM Andor Molnar wrote: > > Fix submitted. > > > On Fri, 2023-06-16 at 14:07 +0200, Andor Molnar wrote: > > Yeah, sorry, I've submitted the patch which broke the build. My first > > thought was to revert

Re: ZooKeeper release 3.9.0

Sirius, Il giorno ven 16 giu 2023 alle ore 15:09 Yang Sirius ha scritto: > > Hi Andor, > > I am writing to inquire about the possibility to include the TLA+ > specifications for ZooKeeper in the upcoming release, version 3.9.0. The > proposal to provide TLA+ specifications for ZooKeeper was

Re: Current master branch is broker

Fix submitted. On Fri, 2023-06-16 at 14:07 +0200, Andor Molnar wrote: > Yeah, sorry, I've submitted the patch which broke the build. My first > thought was to revert immediately and let the contributor to fix it, > but Kezhu already opened a PR with the fix. > > Once the build is greeen, I'm

Re: ZooKeeper release 3.9.0

Hi Andor, I am writing to inquire about the possibility to include the TLA+ specifications for ZooKeeper in the upcoming release, version 3.9.0. The proposal to provide TLA+ specifications for ZooKeeper was raised in ZOOKEEPER-3615, and

Re: Current master branch is broker

Yeah, sorry, I've submitted the patch which broke the build. My first thought was to revert immediately and let the contributor to fix it, but Kezhu already opened a PR with the fix. Once the build is greeen, I'm submitting it with the title: ZOOKEEPER-4655: [ADDENDUM] fix build error Thanks

Re: Current master branch is broker

Thank you Kezhu! This case somehow indicates that we're under a "high" traffic. lol. Best, tison. Kezhu Wang 于2023年6月16日周五 19:20写道： > Hi Enrico, > > I presented a fix https://github.com/apache/zookeeper/pull/2012. > > On Fri, Jun 16, 2023 at 6:47 PM Enrico Olivelli > wrote: > > > > Hello

Re: Current master branch is broker

Hi Enrico, I presented a fix https://github.com/apache/zookeeper/pull/2012. On Fri, Jun 16, 2023 at 6:47 PM Enrico Olivelli wrote: > > Hello ZooKeepers, > > Current master branch is broken, see the errors below. > > Maybe we committed patches and there were some unexpected conflicts >

Review request for ZOOKEEPER-3615

Hi zk folks! I wonder if there is any possibility of including the TLA+ specifications for ZooKeeper in the upcoming release, version 3.9.0. The proposal to provide TLA+ specifications for ZooKeeper was raised in ZOOKEEPER-3615 [1], and addressed via pull request #1690 on github [2]. Formal

Current master branch is broker

Hello ZooKeepers, Current master branch is broken, see the errors below. Maybe we committed patches and there were some unexpected conflicts undetected by git. Enrico [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:testCompile (default-testCompile) on

Re: Name of sequence node is not unique

Li, Il giorno ven 16 giu 2023 alle ore 11:43 Li Wang ha scritto: > > Thanks for the comments and inputs, Ted, Josef and Kezhu. The discussions > are great. > > > The invariant is that the value should be increasing except in > failure modes. You found a somewhat surprising failure mode. > Does

Re: Name of sequence node is not unique

Thanks for the comments and inputs, Ted, Josef and Kezhu. The discussions are great. > The invariant is that the value should be increasing except in failure modes. You found a somewhat surprising failure mode. Does this mean the value is supposed to be always increasing, never decreasing or

TAC Applications for Community Over Code North America and Asia now open

Hi All, (This email goes out to all our user and dev project mailing lists, so you may receive this email more than once.) The Travel Assistance Committee has opened up applications to help get people to the following events: *Community Over Code Asia 2023 - * *August 18th to August 20th in