[jira] [Created] (CURATOR-384) EnsembleTacker.configToConnectionString can render connection impossible

Rhys Yarranton created CURATOR-384: -- Summary: EnsembleTacker.configToConnectionString can render connection impossible Key: CURATOR-384 URL: https://issues.apache.org/jira/browse/CURATOR-384 Project:

[GitHub] curator issue #197: [CURATOR-367] Delay reconnect on session expired

Github user cammckenzie commented on the issue: https://github.com/apache/curator/pull/197 I've run through some more tests and it all looks good. My only concern is that we're introducing the Mockito just for this test case. Could you move the test case into the curator-clien

[jira] [Commented] (CURATOR-367) Curator may deliver RECONNECTED before LOST in case of session expiry

[ https://issues.apache.org/jira/browse/CURATOR-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855024#comment-15855024 ] ASF GitHub Bot commented on CURATOR-367: Github user cammckenzie commented on the

[GitHub] curator issue #197: [CURATOR-367] Delay reconnect on session expired

Github user Randgalt commented on the issue: https://github.com/apache/curator/pull/197 I'm -1 on introducing a new dependency. Can the PR be re-worked to not use Mockito? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[jira] [Commented] (CURATOR-367) Curator may deliver RECONNECTED before LOST in case of session expiry

[ https://issues.apache.org/jira/browse/CURATOR-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855051#comment-15855051 ] ASF GitHub Bot commented on CURATOR-367: Github user Randgalt commented on the is