Re: DISCUSS: Remove Classic connection handling

To clarify, this means that folks still on Curator 2.x will see a change in behavior if they go straight to 4.x? It's a major version, so that should be fine but let's make sure it shows up in the release notes. On Mon, Jul 24, 2017 at 12:01 AM, Jordan Zimmerman < jor...@jordanzimmerman.com> wrote

[jira] [Resolved] (CURATOR-313) Verify that Curator logging is appropriate

[ https://issues.apache.org/jira/browse/CURATOR-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved CURATOR-313. --- Resolution: Not A Problem Thanks for looking, Jordan. I knew that it wasn't an issue anymor

[jira] [Assigned] (CURATOR-313) Verify that Curator logging is appropriate

[ https://issues.apache.org/jira/browse/CURATOR-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reassigned CURATOR-313: - Assignee: (was: Mike Drob) > Verify that Curator logging is appropri

[jira] [Resolved] (CURATOR-414) Typo in TestingZooKeeperMain

[ https://issues.apache.org/jira/browse/CURATOR-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved CURATOR-414. --- Resolution: Fixed LGTM. Thanks for the patch, [~coheigea]! > Typo in TestingZooKeeperM

[jira] [Assigned] (CURATOR-414) Typo in TestingZooKeeperMain

[ https://issues.apache.org/jira/browse/CURATOR-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reassigned CURATOR-414: - Assignee: Mike Drob (was: Jordan Zimmerman) > Typo in TestingZooKeeperM

[jira] [Commented] (CURATOR-404) AsyncTransactionOp#create returns the wrong DSL type

[ https://issues.apache.org/jira/browse/CURATOR-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990146#comment-15990146 ] Mike Drob commented on CURATOR-404: --- Why 99.9%? What's the client that brea

[jira] [Commented] (CURATOR-200) Proposal: Remove references to guava library from public APIs

[ https://issues.apache.org/jira/browse/CURATOR-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812670#comment-15812670 ] Mike Drob commented on CURATOR-200: --- Ah! I misread the diff and see this now. T

[jira] [Commented] (CURATOR-200) Proposal: Remove references to guava library from public APIs

[ https://issues.apache.org/jira/browse/CURATOR-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15808524#comment-15808524 ] Mike Drob commented on CURATOR-200: --- I think we also need to relocate that cla

Re: [VOTE] Release Apache Curator version 2.11.0 and 3.2.0

Yea, as long as you doc it somewhere, it shouldn't be a blocker. On Sat, Jun 18, 2016 at 4:59 PM, Cameron McKenzie wrote: > That's fine with me. You OK with it Mike? > On 19 Jun 2016 1:21 AM, "Jordan Zimmerman" > wrote: > > > Can we solve this at a different time? People are waiting on this rel

Re: [VOTE] Release Apache Curator version 2.11.0 and 3.2.0

-1 Downloaded artifacts from staging repos. Signatures are good. Checksums are good. Source zips does not match tag: $ diff --recursive . /tmp/curator/2.11/apache-curator-2.11.0/ Only in /tmp/curator/2.11/apache-curator-2.11.0/curator-framework: test-output Only in /tmp/curator/2.11/apache-curat

[jira] [Created] (CURATOR-313) Verify that Curator logging is appropriate

Mike Drob created CURATOR-313: - Summary: Verify that Curator logging is appropriate Key: CURATOR-313 URL: https://issues.apache.org/jira/browse/CURATOR-313 Project: Apache Curator Issue Type

[jira] [Commented] (CURATOR-262) Issue with ExponentialBackoffRetry

[ https://issues.apache.org/jira/browse/CURATOR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168141#comment-15168141 ] Mike Drob commented on CURATOR-262: --- [~ddyankov] - I think you are correct. Would

[jira] [Updated] (CURATOR-262) Issue with ExponentialBackoffRetry

[ https://issues.apache.org/jira/browse/CURATOR-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-262: -- Labels: newbie (was: ) > Issue with ExponentialBackoffRe

Re: [VOTE] Release Apache Curator version 2.10.0 and 3.1.0, RC2

All 2.10 tests pass. Most 3.1 tests pass, the ones that didn't pass did so when rerun in isolation. Signatures match zip file Zip file matches source tag Licence headers look good. Compatibility reports look good. +1 to both (binding) On Thu, Feb 11, 2016 at 10:52 AM, David Kesler wrote: > Gotc

[jira] [Resolved] (CURATOR-281) Usage of TestingServer fails when upgrading to 3.0

[ https://issues.apache.org/jira/browse/CURATOR-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved CURATOR-281. --- Resolution: Fixed Assignee: Mike Drob (was: Jordan Zimmerman) Fix Version/s: 3.0.1

[jira] [Commented] (CURATOR-278) In transactions compressed option does not work with some fluent api combinations

[ https://issues.apache.org/jira/browse/CURATOR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999359#comment-14999359 ] Mike Drob commented on CURATOR-278: --- Also, need to check for conflicts with CUR

[jira] [Assigned] (CURATOR-278) In transactions compressed option does not work with some fluent api combinations

[ https://issues.apache.org/jira/browse/CURATOR-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reassigned CURATOR-278: - Assignee: Mike Drob The patch looks pretty good, thank you for submitting it, Grant! I need to

Namespace client must be started

Curators, I noticed earlier today that client.usingNamespace() has a precondition check for whether it's been started or not. Is there a reason for this? I could imagine a scenario where you prepare a client by namespacing it and then don't start it until later when you need to do your actual ope

[jira] [Commented] (CURATOR-280) LeaderLatch doesn't work when using a zookeeper chroot

[ https://issues.apache.org/jira/browse/CURATOR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998877#comment-14998877 ] Mike Drob commented on CURATOR-280: --- I suspect that it will work with an exis

[jira] [Commented] (CURATOR-280) LeaderLatch doesn't work when using a zookeeper chroot

[ https://issues.apache.org/jira/browse/CURATOR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998792#comment-14998792 ] Mike Drob commented on CURATOR-280: --- Does the chroot exist beforehand? Not sure i

Re: [VOTE] Release Apache Curator version 2.9.1

+1 Verified signatures and checksums. Verified compatibility with 2.9.0 release. Contents of zip file have 777 permissions, which probably isn't a huge issue but is mildly annoying/surprising. Cam, are you building on Windows, by chance? On Thu, Oct 29, 2015 at 12:48 PM, Jordan Zimmerman < jor..

Re: [VOTE] Release Apache Curator version 2.9.1

I'm looking at the RC in between other [dayjob] responsibilities right now, and should get a chance to post a vote in the next couple hours. Not sure if I'll make the 72 hours, I hope that's not a strict deadline and more of a guideline. Mike On Thu, Oct 29, 2015 at 12:11 PM, Jordan Zimmerman < j

Re: ETA on Curator 2.9.1

It should be prompting you for what to name the tags, unless something changed recently. If not, check out the arguments for batch mode: http://maven.apache.org/maven-release/maven-release-plugin/examples/non-interactive-release.html Might need to specify -Dtag=apache-curator-2.9.1 -DreleaseVersio

Re: https://github.com/apache/curator/pull/99

Sorry for the delay, Jordan, I've been traveling recently. My implementing in the PR is not complete, if I'm holding up a release probably safe to bump to the next version. I'll try to wrap things up next week. On Fri, Oct 16, 2015, 1:32 PM Jordan Zimmerman wrote: > Can one of the other dev tr

Re: [ANNOUNCE] Apache Curator 2.9.0 released

Jordan, can you mark the fix version as released in JIRA when you get a chance? https://issues.apache.org/jira/browse/CURATOR/fixforversion/12332392 On Thu, Sep 10, 2015 at 12:21 PM, Mike Drob wrote: > Hello, > > The Apache Curator team is pleased to announce the release of vers

[ANNOUNCE] Apache Curator 2.9.0 released

Hello, The Apache Curator team is pleased to announce the release of version 2.9.0. The Apache Curator Java libraries make using Apache ZooKeeper much easier and more reliable. Link to release notes:https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332392&projectId=12314425

[RESULT] [VOTE] Release Apache Curator 2.9.0

The vote to release Curator 2.9.0 has passed. +1 (binding): Mike Drob Jordan Zimmerman Cameron McKenzie I will promote the artifacts to the central repo. Mike

Re: [2/5] curator git commit: [maven-release-plugin] prepare release apache-curator-2.9.0-rc1

I sent it, but forgot to include a subject. Will resend. On Thu, Sep 10, 2015 at 12:14 PM, Jordan Zimmerman < jor...@jordanzimmerman.com> wrote: > Did you send the vote results email? I didn’t see it. > > -Jordan > > > > On September 10, 2015 at 12:13:27 PM, Mik

Re: [2/5] curator git commit: [maven-release-plugin] prepare release apache-curator-2.9.0-rc1

Not another release. It's the same thing that was pushed before. I added a new tag for the non-rc released version on the same commit and pushed that + master. On Thu, Sep 10, 2015 at 12:08 PM, Jordan Zimmerman < jor...@jordanzimmerman.com> wrote: > Mike, > > Why is another release being created?

Re: [VOTE] Release Apache Curator version 2.9.0

Sorry for the delay, I was travelling over the long weekend in the US. This vote passes with 3 +1 votes and no other votes. Will publish artifacts and update website shortly. +1 votes: Mike Drob Jordan Zimmerman Cameron McKenzie Thanks, Mike On Wed, Sep 2, 2015 at 1:10 PM, Mike Drob wrote

Re: Git Push Summary

off this tag so I could run the tests etc. > > On Thu, Sep 3, 2015 at 4:18 AM, Jordan Zimmerman < > jor...@jordanzimmerman.com > > wrote: > > > I meant Maven encryption. You had the right ref. > > > > > > > > On September 2, 2015 at 11:16:47 AM, Mike Drob (md...@apache.org) > wrote: > > > > https://maven.apache.org/guides/mini/guide-encryption.html > >

Re: [VOTE] Release Apache Curator version 2.9.0

Yes. Did you import it? On Wed, Sep 2, 2015, 4:07 PM Jordan Zimmerman wrote: > gpg: Signature made Wed Sep 2 10:59:33 2015 PDT using RSA key ID EF362B9E > > gpg: Good signature from "Mike Drob (CODE SIGNING KEY) " > [unknown] > > gpg: WARNING: This key is not certif

Re: Git Push Summary

What's Maven encoding? On Wed, Sep 2, 2015 at 1:15 PM, Jordan Zimmerman wrote: > Ah, OK. What I meant was using Maven encoding. Please update the wiki with > your understanding so that it’s clear. > > -Jordan > > > > On September 2, 2015 at 11:14:17 AM, Mike

Re: Git Push Summary

In the wiki page https://cwiki.apache.org/confluence/display/CURATOR/For+Curator+Committers#ForCuratorCommitters-maven-settings it tells me to use APACHE-PASSWORD-ENCODED. I thought this meant to use an encrypted password a la https://maven.apache.org/guides/mini/guide-encryption.html When I switc

[VOTE] Release Apache Curator version 2.9.0

Hello, This is the vote for Apache Curator version 2.9.0 *** Please download, test and vote within approx. 72 hours Note that we are voting upon the source (tag) and binaries are provided for convenience. Link to release notes:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123

Re: Status on 2.9.0

gt; > -Jordan > > On September 1, 2015 at 2:42:55 PM, Mike Drob (mad...@cloudera.com) wrote: > > Hey all, I was trying to build and put up a release candidate following > the instructions on the wiki, but ran into > > [ERROR] Failed to execute goal > org.apache.mav

Re: Status on 2.9.0

Hey all, I was trying to build and put up a release candidate following the instructions on the wiki, but ran into [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project apache-curator: Failed to deploy artifacts: Could not transfer

[jira] [Commented] (CURATOR-256) Provide curator artifact in Maven Central with Guava shaded away

[ https://issues.apache.org/jira/browse/CURATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725558#comment-14725558 ] Mike Drob commented on CURATOR-256: --- bq. Later releases of Guava are largely backw

[jira] [Commented] (CURATOR-256) Provide curator artifact in Maven Central with Guava shaded away

[ https://issues.apache.org/jira/browse/CURATOR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724619#comment-14724619 ] Mike Drob commented on CURATOR-256: --- I think I would prefer the approach in CUR

Re: Status on 2.9.0

Ack! Apologies, apologies. I will make time for an RC this week. On Sunday, August 30, 2015, Cameron McKenzie wrote: > You are indeed correct! I was referring to CURATOR-228. > > On Mon, Aug 31, 2015 at 8:48 AM, Jordan Zimmerman < > jor...@jordanzimmerman.com > wrote: > > > CURATOR-233? Do you

[jira] [Commented] (CURATOR-253) Use new injectSessionExpiration() in the test module

[ https://issues.apache.org/jira/browse/CURATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720454#comment-14720454 ] Mike Drob commented on CURATOR-253: --- Oh. Scratch that plan, then. >

[jira] [Commented] (CURATOR-253) Use new injectSessionExpiration() in the test module

[ https://issues.apache.org/jira/browse/CURATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720439#comment-14720439 ] Mike Drob commented on CURATOR-253: --- bq. Hmm - the only problem is where to put it

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

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715221#comment-14715221 ] Mike Drob commented on CURATOR-233: --- Ah, yes, I misunderstood the shortcut. Now

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

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715219#comment-14715219 ] Mike Drob commented on CURATOR-233: --- Yea, that's probably ok. I didn'

Re: CURATOR-217?

> You'd never want to do that to master, a release branch, or someone > >> > else's > >> > > branch. > >> > > On Aug 24, 2015 11:15 PM, "Cameron McKenzie" < > mckenzie@gmail.com> > >> > > wrote: > &

[jira] [Commented] (CURATOR-161) Support Watcher Removal

[ https://issues.apache.org/jira/browse/CURATOR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711894#comment-14711894 ] Mike Drob commented on CURATOR-161: --- Oh, I didn't know we had that. Ran it a

[jira] [Comment Edited] (CURATOR-161) Support Watcher Removal

[ https://issues.apache.org/jira/browse/CURATOR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711780#comment-14711780 ] Mike Drob edited comment on CURATOR-161 at 8/25/15 6:5

[jira] [Commented] (CURATOR-161) Support Watcher Removal

[ https://issues.apache.org/jira/browse/CURATOR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711780#comment-14711780 ] Mike Drob commented on CURATOR-161: --- {noformat} [INFO] Missing header in: cur

Re: Build failed in Jenkins: Curator-3.0 #4

Apologies for the noise here. When I initially configured the Curator-3.0 job, I missed that it needed to be Java 7, so we're ending up with a few failed builds because of that. On Tue, Aug 25, 2015 at 1:19 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

DistributedDoubleBarrier semantics

Devs, I was working on CURATOR-233 and I realized that I don't really understand the semantics of the DistributedDoubleBarrier when there are more clients than the given member quantity. Note that I'm not asking about what the code currently does (because I suspect it has a few inconsistencies) bu

Re: CURATOR-217?

e about fast-forwards' in 'git push --help' for details. > > There have been no changes on the branch since I did the pull before the > rebase. > > Any ideas? > > > > > > > On Tue, Aug 25, 2015 at 8:48 AM, Cameron McKenzie > wrote: > >

Re: CURATOR-217?

if you're going to tray that, here's what you want to do (assuming command line) git checkout CURATOR-167 # start with the branch that you are changing git rebase -i master # rebase the current branch on top of the given branch On Mon, Aug 24, 2015 at 5:07 PM, Cameron McKenzie wrote: > Scott, >

[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 ] Mike Drob updated CURATOR-233: -- Fix Version/s: (was: awaiting-response) 2.9.0 [~Lianro] - Please check out my

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

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reassigned CURATOR-233: - Assignee: Mike Drob > Bug in double barrier > - > >

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

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709692#comment-14709692 ] Mike Drob commented on CURATOR-233: --- Ah, I think I see what you are saying. I did

[jira] [Commented] (CURATOR-217) Use new Watcher Removal APIs in Curator Recipes

[ https://issues.apache.org/jira/browse/CURATOR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709486#comment-14709486 ] Mike Drob commented on CURATOR-217: --- The PR is closed, was this merged in? Can

[DISCUSS] Releasing Curator 2.9

Devs, First, a big thanks to Jordan for fixing the two test failures that we've been seeing. I'm going to try and get Curator 2.9 ready for release. There is one remaining issue open - CURATOR-167 Once that is resolved, I'm going to run through

[jira] [Resolved] (CURATOR-234) Add test logging back to modules

[ https://issues.apache.org/jira/browse/CURATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved CURATOR-234. --- Resolution: Fixed Added test logging to curator-x modules and verified output manually. > Add t

[jira] [Commented] (CURATOR-167) All registered watchers should be cleared on close

[ https://issues.apache.org/jira/browse/CURATOR-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709470#comment-14709470 ] Mike Drob commented on CURATOR-167: --- [~cammckenzie] - Can you make sure that the P

[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 ] Mike Drob updated CURATOR-233: -- Fix Version/s: (was: 2.9.0) awaiting-response > Bug in double barr

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

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709379#comment-14709379 ] Mike Drob commented on CURATOR-233: --- Hi Lianro. I tried to convert your example in

[jira] [Commented] (CURATOR-252) TestLeaderSelectorEdges::createProtectedNodeInBackgroundTest failed

[ https://issues.apache.org/jira/browse/CURATOR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709289#comment-14709289 ] Mike Drob commented on CURATOR-252: --- When there are timing related failures, the

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

[ https://issues.apache.org/jira/browse/CURATOR-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved CURATOR-218. --- Resolution: Fixed Assignee: Mike Drob (was: Jordan Zimmerman) Ran into this issue again when

[jira] [Commented] (CURATOR-234) Add test logging back to modules

[ https://issues.apache.org/jira/browse/CURATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708394#comment-14708394 ] Mike Drob commented on CURATOR-234: --- In https://github.com/apache/curator/co

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

[ https://issues.apache.org/jira/browse/CURATOR-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-242: -- Component/s: Recipes > TestDistributedQueue.testCustomExecutor() is fail

[jira] [Updated] (CURATOR-252) TestLeaderSelectorEdges::createProtectedNodeInBackgroundTest failed

[ https://issues.apache.org/jira/browse/CURATOR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-252: -- Affects Version/s: (was: 2.9.0) Priority: Blocker (was: Major) Fix Version/s

[jira] [Created] (CURATOR-252) TestLeaderSelectorEdges::createProtectedNodeInBackgroundTest failed

Mike Drob created CURATOR-252: - Summary: TestLeaderSelectorEdges::createProtectedNodeInBackgroundTest failed Key: CURATOR-252 URL: https://issues.apache.org/jira/browse/CURATOR-252 Project: Apache

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

[ https://issues.apache.org/jira/browse/CURATOR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-243: -- Component/s: Recipes > TestDistributedIdQueue.testRequeuingWithLock is fail

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

[ https://issues.apache.org/jira/browse/CURATOR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-243: -- Labels: jenkins (was: ) > TestDistributedIdQueue.testRequeuingWithLock is fail

[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 ] Mike Drob updated CURATOR-231: -- Labels: jenkins (was: ) > TestDistributedQueue.testRetryAfterFailure_Curator56 fa

[jira] [Created] (CURATOR-251) TestResetConnectionWithBackgroundFailure::testConnectionStateListener failing

Mike Drob created CURATOR-251: - Summary: TestResetConnectionWithBackgroundFailure::testConnectionStateListener failing Key: CURATOR-251 URL: https://issues.apache.org/jira/browse/CURATOR-251 Project

Re: Next Steps

https://builds.apache.org/job/Curator-3.0/ On Fri, Aug 21, 2015 at 12:54 PM, Jordan Zimmerman < jor...@jordanzimmerman.com> wrote: > Good idea. You should have perms to create it. If not, let me know. > > > > On August 21, 2015 at 12:53:39 PM, Mike Drob (md...@apache.org)

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

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707361#comment-14707361 ] Mike Drob commented on CURATOR-233: --- Hi J D! Thanks for attaching your test cas

[jira] [Resolved] (CURATOR-250) CURATOR-224 caused regression of CURATOR-56

[ https://issues.apache.org/jira/browse/CURATOR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved CURATOR-250. --- Resolution: Duplicate Dup of CURATOR-231? > CURATOR-224 caused regression of CURATOR

Re: Next Steps

Is there a curator-3.0 jenkins job? On Wed, Aug 19, 2015 at 4:47 PM, Cameron McKenzie wrote: > Nope, all sorted. > Thanks. > > On Thu, Aug 20, 2015 at 6:29 AM, Jordan Zimmerman < > jor...@jordanzimmerman.com> wrote: > > > Resending - is there something I need to do on watchers? > > > > -Jordan >

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

[ https://issues.apache.org/jira/browse/CURATOR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707133#comment-14707133 ] Mike Drob commented on CURATOR-243: --- Does this need to be merged into

[jira] [Commented] (CURATOR-249) Update all Curator recipes to use new pluggable Error Handler

[ https://issues.apache.org/jira/browse/CURATOR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706754#comment-14706754 ] Mike Drob commented on CURATOR-249: --- I can do this once the error handlers are

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

[ https://issues.apache.org/jira/browse/CURATOR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699588#comment-14699588 ] Mike Drob commented on CURATOR-243: --- The logs from this test make me think that i

Re: Next Steps

. I'd suggest > anything > > > for > > > > > 2.x > > > > > > goes into master and then we immediately merge master into 3.0. > > > > Anything > > > > > > for 3.0 stays in 3.0 only. (There will soon be a discussion to > be

[jira] [Resolved] (CURATOR-234) Add test logging back to modules

[ https://issues.apache.org/jira/browse/CURATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved CURATOR-234. --- Resolution: Fixed Fix Version/s: 2.9.0 Jenkins is back to completing. > Add test logg

[jira] [Commented] (CURATOR-234) Add test logging back to modules

[ https://issues.apache.org/jira/browse/CURATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697781#comment-14697781 ] Mike Drob commented on CURATOR-234: --- I pushed this, but the added logging made

[jira] [Assigned] (CURATOR-234) Add test logging back to modules

[ https://issues.apache.org/jira/browse/CURATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob reassigned CURATOR-234: - Assignee: Mike Drob > Add test logging back to modu

[jira] [Work started] (CURATOR-234) Add test logging back to modules

[ https://issues.apache.org/jira/browse/CURATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CURATOR-234 started by Mike Drob. - > Add test logging back to modu

Re: Next Steps

Once we have a stable 3.0 branch, should we dual-commit everything to master and 3.x? The ZK3.5 "alpha" labelling can scare off some adopters, so I think it is important to maintain 2.x for a little while longer. I can volunteer to do the next 2.x release once the tests are stabilized - I'll start

[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

[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

[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

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14662282#comment-14662282 ] Mike Drob commented on CURATOR-129: --- I just pushed this change. Can somebody look

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

[ https://issues.apache.org/jira/browse/CURATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652442#comment-14652442 ] Mike Drob commented on CURATOR-231: --- Note that this is still failing. h

[jira] [Commented] (CURATOR-240) Severe memory leak in TreeCache when path does not exist

[ https://issues.apache.org/jira/browse/CURATOR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649738#comment-14649738 ] Mike Drob commented on CURATOR-240: --- I had spent a little bit of time looking at

Re: [ANN] Apache Curator welcomes Mike Drob as a new Committer and PMC member.

14 PM, Cameron McKenzie wrote: > The Apache Curator project is happy to announce that Mike Drob > (md...@apache.org ) is a now a committer and PMC > member of the > project. Mike has been a great member of the Curator community and > will be a great addition to the team. > >

[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=14638099#comment-14638099 ] Mike Drob commented on CURATOR-228: --- Logging a message is a reasonable first

[jira] [Commented] (CURATOR-238) Create code style file for NetBeans

[ https://issues.apache.org/jira/browse/CURATOR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634127#comment-14634127 ] Mike Drob commented on CURATOR-238: --- My original plan was wiki, next to the orig

[jira] [Commented] (CURATOR-238) Create code style file for NetBeans

[ https://issues.apache.org/jira/browse/CURATOR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14634113#comment-14634113 ] Mike Drob commented on CURATOR-238: --- Yea, this is meant to be more of a guideline

[jira] [Updated] (CURATOR-238) Create code style file for NetBeans

[ https://issues.apache.org/jira/browse/CURATOR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-238: -- Attachment: netbeans.zip Attached is a tentative style file created in NetBeans 8.0 editor. It was

[jira] [Created] (CURATOR-238) Create code style file for NetBeans

Mike Drob created CURATOR-238: - Summary: Create code style file for NetBeans Key: CURATOR-238 URL: https://issues.apache.org/jira/browse/CURATOR-238 Project: Apache Curator Issue Type: Sub-task

[jira] [Created] (CURATOR-237) [Parent] Create code style files for other IDEs

Mike Drob created CURATOR-237: - Summary: [Parent] Create code style files for other IDEs Key: CURATOR-237 URL: https://issues.apache.org/jira/browse/CURATOR-237 Project: Apache Curator Issue

[jira] [Commented] (CURATOR-232) Consolidate test code

[ https://issues.apache.org/jira/browse/CURATOR-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632917#comment-14632917 ] Mike Drob commented on CURATOR-232: --- Updated PR that adds feature

Re: Can somebody look at open PRs?

> > > > On July 14, 2015 at 12:35:15 PM, Mike Drob (md...@apache.org) wrote: > > Hey Curator Devs! > > I've got a few open PRs, and was hoping somebody would be willing to take > a > look at some/all of them. > > In roughly priority order - > > https:

Can somebody look at open PRs?

Hey Curator Devs! I've got a few open PRs, and was hoping somebody would be willing to take a look at some/all of them. In roughly priority order - https://issues.apache.org/jira/browse/CURATOR-234 - Test Logging https://issues.apache.org/jira/browse/CURATOR-218 - BlockUntilConnected Race Condit

  1   2   3   >