See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1414/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 76 lines...]
ivy-taskdef:
ivy-init:
ivy-retrieve:
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731197#comment-15731197
]
Michael Han commented on ZOOKEEPER-2202:
I agree with what Alex said - I think
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2352/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 78 lines...]
ivy-retrieve:
[ivy:retrieve] :: Apa
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730910#comment-15730910
]
Alexander Shraer commented on ZOOKEEPER-2202:
-
Hi Raul,
To reiterate my p
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730869#comment-15730869
]
Hadoop QA commented on ZOOKEEPER-2202:
--
-1 overall. Here are the results of test
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2202
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3539/
###
## LAST 60 LINES OF THE CONSOLE
###
[
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730773#comment-15730773
]
Raul Gutierrez Segales commented on ZOOKEEPER-2202:
---
[~hanm], [~phun
Patrick,
The 'dummy commit' is a Github trick. In any commit message you can write
"closes #", like "closes #84" (by my own experience you can also
write "fixes #". You can put as many of those messages as you
like in the commit message even if the commit doesn't have relation with
the PRs. Then G
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1269/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
[EnvInject] - Loading node environment variable
It's not about style, there were a number of concerns addressed in that
patch. We didn't take the change lightly, we've been discussing it over
jira and the mailing list over the past two years.
I think people understand what alpha means. There may be some short term
impact for a few, but a signif
I read through the issue and disagree about the decision to move the APIs out.
That was a stylistic choice that breaks client code. I realize that 3.5.x has
been advertised as an alpha but you must realize that most of the world is
using it in production. These APIs have now been published. This
On Wed, Dec 7, 2016 at 2:09 PM, Patrick Hunt wrote:
> Interesting, thanks for the update Edward.
>
> "close via a dummy commit" - I don't think that's possible, doesn't GH
> match up a PR to a commit based on the hash?
>
Afaik, yes. I didn't understand what he meant by 'dummy commit', tbqh.
Gon
See https://builds.apache.org/job/ZooKeeper_branch35_solaris/343/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 144517 lines...]
[junit] 2016-12-07 17:06:27,
It's discussed in more depth in the JIRA iirc, but basically;
ZooKeeper.java provides client APIs, reconfig is an admiistrative API.
Patrick
On Wed, Dec 7, 2016 at 8:48 AM, Jordan Zimmerman wrote:
> I understand the need to make the methods require proper auth but there's
> no reason to move it
I understand the need to make the methods require proper auth but there's no
reason to move it to a different class that I can see. Am I missing something?
Jordan Zimmerman
> On Dec 7, 2016, at 4:37 PM, Patrick Hunt wrote:
>
> This problem has been a long standing blocker
Interesting, thanks for the update Edward.
"close via a dummy commit" - I don't think that's possible, doesn't GH
match up a PR to a commit based on the hash?
Patrick
On Tue, Dec 6, 2016 at 6:17 AM, Edward Ribeiro
wrote:
> Oh, Patrick (and Flavio, and Ben Reed),
>
> I asked some questions to
This problem has been a long standing blocker issue for 3.5 and identified
early on as something that would need to change. This has been one of the
reasons why 3.5 has stayed in alpha - because we allow non-backward
compatible changes to new APIs in alpha and we knew we would have to fix
this. The
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1299/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 238663 lines...]
[junit] 2016-12-07 15:33:4
See https://builds.apache.org/job/ZooKeeper_branch34_solaris/1381/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 189628 lines...]
[junit] 2016-12-07 13:55:11
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/848/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 457383 lines...]
[junit] 2016-12-07 12:00:33,314 [m
Jordan Zimmerman created ZOOKEEPER-2642:
---
Summary: ZOOKEEPER-2014 breaks existing clients for little benefit
Key: ZOOKEEPER-2642
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2642
Project:
OK - I found the offending issue: ZOOKEEPER-2014
What is the benefit/logic of moving the reconfig() variants into a new class? I
can see if this was done from the start but you have now broken Curator in a
fairly serious non-backward compatible way for a minor documenting benefit.
Does anyone o
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728484#comment-15728484
]
Jordan Zimmerman commented on ZOOKEEPER-2014:
-
I realize I'm very late to
Hi,
I was compiling Curator against the ZK master and noticed that the reconfig
APIs are gone/changed. Can anyone point me at the issues for this and/or the
discussion why this breaking change was made?
-Jordan
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/323/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
[EnvInject] - Loading node environment variab
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1413/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 463235 lines...]
[junit] 2016-12-07 08:30:43,69
26 matches
Mail list logo
