GitHub user eolivelli opened a pull request:
https://github.com/apache/curator/pull/170
CURATOR-356 Allow SASL configuration for TestingServer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/eolivelli/curator CURATOR-356
Alterna
[
https://issues.apache.org/jira/browse/CURATOR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608288#comment-15608288
]
ASF GitHub Bot commented on CURATOR-356:
GitHub user eolivelli opened a pull requ
Hey everyone,
I was wondering when a release is planed for 2.11.1. My team uses
curator and found that periodically it throws an exception for "You do
not own the lock" this appears fixed in the 2.11.1 version.
I am planning on getting the source code and verify the fix, but needed
to be a
Real Soon Now™ - We’ll do it sometime early November.
-Jordan
> On Oct 26, 2016, at 11:45 AM, Scott Carr wrote:
>
> Hey everyone,
>
> I was wondering when a release is planed for 2.11.1. My team uses curator
> and found that periodically it throws an exception for "You do not own the
> lock
Anything I can do to help?
On 10/26/2016 11:47 AM, Jordan Zimmerman wrote:
Real Soon Now™ - We’ll do it sometime early November.
-Jordan
On Oct 26, 2016, at 11:45 AM, Scott Carr wrote:
Hey everyone,
I was wondering when a release is planed for 2.11.1. My team uses curator and found that
1) I haven’t had a chance to look at the current PRs/Issues. Have a look there
and see if there’s anything in flight or that should be in a 2.11.
2) We could always use help even beyond the next release. We’d love help in
general!
3) Push ZooKeeper to merge my PR on ZOOKEEPER-1525 and to release
[
https://issues.apache.org/jira/browse/CURATOR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609112#comment-15609112
]
Kevin Scott Carr commented on CURATOR-172:
--
I believe this can be closed, as the
[
https://issues.apache.org/jira/browse/CURATOR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Zimmerman closed CURATOR-172.
Resolution: Not A Problem
> Deadlock when performing background operation
> ---
[
https://issues.apache.org/jira/browse/CURATOR-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609172#comment-15609172
]
Kevin Scott Carr commented on CURATOR-188:
--
curator-framework/2.11.0
Seeing thi
Github user asfgit closed the pull request at:
https://github.com/apache/curator/pull/170
---
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 ena
[
https://issues.apache.org/jira/browse/CURATOR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609897#comment-15609897
]
ASF GitHub Bot commented on CURATOR-356:
Github user asfgit closed the pull reque
[
https://issues.apache.org/jira/browse/CURATOR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15609900#comment-15609900
]
ASF GitHub Bot commented on CURATOR-356:
Github user cammckenzie commented on the
[
https://issues.apache.org/jira/browse/CURATOR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cameron McKenzie closed CURATOR-356.
Resolution: Fixed
Fix Version/s: 2.11.1
3.2.1
> Allow SASL config
Github user cammckenzie commented on the issue:
https://github.com/apache/curator/pull/170
Looks good to me, thanks for the PR.
---
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
en
14 matches
Mail list logo
