Re: Next Steps

Right, I'm a bit stuck. I have renamed the old branch and created a new CURATOR-3.0 off master. When I try and merge CURATOR-160, a change to CreateBuilderImpl.java gets merged (I'm not sure why as it doesn't appear on the list of affected files by CURATOR-160), and this removes the 'debugForceFind

Re: Next Steps

Maybe just rename it for now and we can delete it later On August 11, 2015 at 11:28:14 PM, Cameron McKenzie (mckenzie@gmail.com) wrote: So, I will delete the existing CURATOR-3.0 branch? On Wed, Aug 12, 2015 at 2:04 PM, Cameron McKenzie wrote: Sure thing. On Wed, Aug 12, 2015 at 1:55 P

Re: Next Steps

So, I will delete the existing CURATOR-3.0 branch? On Wed, Aug 12, 2015 at 2:04 PM, Cameron McKenzie wrote: > Sure thing. > > On Wed, Aug 12, 2015 at 1:55 PM, Jordan Zimmerman < > jor...@jordanzimmerman.com> wrote: > >> Go ahead, if you don’t mind. >> >> >> >> On August 11, 2015 at 10:50:52 PM,

Re: Next Steps

Sure thing. On Wed, Aug 12, 2015 at 1:55 PM, Jordan Zimmerman < jor...@jordanzimmerman.com> wrote: > Go ahead, if you don’t mind. > > > > On August 11, 2015 at 10:50:52 PM, Cameron McKenzie ( > mckenzie@gmail.com) wrote: > > Ok, I can give that a spin if you like, or I'm happy for you to do i

Re: Next Steps

Go ahead, if you don’t mind. On August 11, 2015 at 10:50:52 PM, Cameron McKenzie (mckenzie@gmail.com) wrote: Ok, I can give that a spin if you like, or I'm happy for you to do it and I'll branch from there for CURATOR-214. On Wed, Aug 12, 2015 at 1:42 PM, Jordan Zimmerman wrote: Is it

Re: Next Steps

Ok, I can give that a spin if you like, or I'm happy for you to do it and I'll branch from there for CURATOR-214. On Wed, Aug 12, 2015 at 1:42 PM, Jordan Zimmerman < jor...@jordanzimmerman.com> wrote: > Is it just a matter of > branching off master and merging all of the CURATOR-3.0 related branc

Re: Next Steps

Is it just a matter of  branching off master and merging all of the CURATOR-3.0 related branches?  Yes, that’s my plan anyway. On August 11, 2015 at 10:39:25 PM, Cameron McKenzie (mckenzie@gmail.com) wrote: My git knowledge is not deep enough to work out what's going on with the CURATO

[jira] [Commented] (CURATOR-228) A serious death cycle error(一个严重的死循环错误)

[ https://issues.apache.org/jira/browse/CURATOR-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692864#comment-14692864 ] Cameron McKenzie commented on CURATOR-228: -- The argument from the guys on the de

Re: Next Steps

My git knowledge is not deep enough to work out what's going on with the CURATOR-3.0 branch, so I'm happy to go from scratch. Is it just a matter of branching off master and merging all of the CURATOR-3.0 related branches? On Wed, Aug 12, 2015 at 1:26 PM, Jordan Zimmerman < jor...@jordanzimmerman.

[jira] [Commented] (CURATOR-228) A serious death cycle error(一个严重的死循环错误)

[ https://issues.apache.org/jira/browse/CURATOR-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692849#comment-14692849 ] Jordan Zimmerman commented on CURATOR-228: -- I still feel that this is a client e

Re: Next Steps

We need to come to a decision on the CURATOR-3.0 branch. My gut instinct is to start from scratch. Any other ideas? -JZ On August 11, 2015 at 5:28:30 PM, Cameron McKenzie (mckenzie@gmail.com) wrote: Also, which branch should the CURATOR-214 fix come off? From memory the CURATOR-3.0 bran

[jira] [Resolved] (CURATOR-241) PersistentEphemeralNode writes initial data on reconnect

[ https://issues.apache.org/jira/browse/CURATOR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie resolved CURATOR-241. -- Resolution: Fixed > PersistentEphemeralNode writes initial data on reconnect >

[jira] [Commented] (CURATOR-241) PersistentEphemeralNode writes initial data on reconnect

[ https://issues.apache.org/jira/browse/CURATOR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692389#comment-14692389 ] ASF GitHub Bot commented on CURATOR-241: Github user asfgit closed the pull reque

[jira] [Updated] (CURATOR-241) PersistentEphemeralNode writes initial data on reconnect

[ https://issues.apache.org/jira/browse/CURATOR-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cameron McKenzie updated CURATOR-241: - Fix Version/s: 2.9.0 > PersistentEphemeralNode writes initial data on reconnect > ---

[GitHub] curator pull request: CURATOR-241: Write updated data on reconnect

Github user asfgit closed the pull request at: https://github.com/apache/curator/pull/95 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

Re: Next Steps

Also, which branch should the CURATOR-214 fix come off? From memory the CURATOR-3.0 branch was broken in some capacity. Should I be branching off CURATOR-3.0-temp or something else? cheers On Wed, Aug 12, 2015 at 8:09 AM, Cameron McKenzie wrote: > Will do. In the meantime could you please have a

Re: Next Steps

Will do. In the meantime could you please have a look at my suggested solution for CURATOR-228 (It's in the JIRA)? I don't want to start work on it until we have an agreed solution. cheers On Wed, Aug 12, 2015 at 12:23 AM, Jordan Zimmerman < jor...@jordanzimmerman.com> wrote: > Hi Cameron, > > Go

[jira] [Commented] (CURATOR-228) A serious death cycle error(一个严重的死循环错误)

[ https://issues.apache.org/jira/browse/CURATOR-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692341#comment-14692341 ] Cameron McKenzie commented on CURATOR-228: -- I've looked into this a bit more and

[jira] [Created] (CURATOR-244) Creating parents with ACLProvider puts wrong ACLs on znodes

John Vines created CURATOR-244: -- Summary: Creating parents with ACLProvider puts wrong ACLs on znodes Key: CURATOR-244 URL: https://issues.apache.org/jira/browse/CURATOR-244 Project: Apache Curator

[jira] [Updated] (CURATOR-231) TestDistributedQueue.testRetryAfterFailure_Curator56 fails

[ https://issues.apache.org/jira/browse/CURATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-231: - Fix Version/s: 2.9.0 > TestDistributedQueue.testRetryAfterFailure_Curator56 fails > -

[jira] [Resolved] (CURATOR-129) Two of PathChildrenCache's constructors need better doc

[ https://issues.apache.org/jira/browse/CURATOR-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved CURATOR-129. --- Resolution: Fixed Assignee: Mike Drob Fix Version/s: 2.9.0 Thanks for looking, Jordan

[jira] [Created] (CURATOR-243) TestDistributedIdQueue.testRequeuingWithLock is failing

Mike Drob created CURATOR-243: - Summary: TestDistributedIdQueue.testRequeuingWithLock is failing Key: CURATOR-243 URL: https://issues.apache.org/jira/browse/CURATOR-243 Project: Apache Curator Is

[jira] [Created] (CURATOR-242) TestDistributedQueue.testCustomExecutor() is failing

Mike Drob created CURATOR-242: - Summary: TestDistributedQueue.testCustomExecutor() is failing Key: CURATOR-242 URL: https://issues.apache.org/jira/browse/CURATOR-242 Project: Apache Curator Issue

Jenkins build is still unstable: Curator #940

See

Jenkins build is still unstable: Curator » Curator Recipes #940

See

[jira] [Updated] (CURATOR-233) Bug in double barrier

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-233: - Fix Version/s: 2.9.0 > Bug in double barrier > - > >

[jira] [Updated] (CURATOR-218) Race condition in client.blockUntilConnected()

[ https://issues.apache.org/jira/browse/CURATOR-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-218: - Fix Version/s: 2.9.0 > Race condition in client.blockUntilConnected() > -

Re: Next Steps

Hi Cameron, Go ahead and do CURATOR-214 - I assigned it to you. -JZ On August 9, 2015 at 6:47:50 PM, Cameron McKenzie (mckenzie@gmail.com) wrote: Sounds reasonable, what's left for 3.0.0? I think that watcher removal is done. So just the host provider (https://issues.apache.org/jira/br

[jira] [Updated] (CURATOR-214) Support new create() APIs

[ https://issues.apache.org/jira/browse/CURATOR-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-214: - Assignee: Cameron McKenzie (was: Jordan Zimmerman) > Support new create() APIs > ---