[jira] Updated: (ZOOKEEPER-615) wrong javadoc for create with a sequence flag

[ https://issues.apache.org/jira/browse/ZOOKEEPER-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-615: Hadoop Flags: [Reviewed] Status: Patch Available (was: Open) +1 brilliant pro

[jira] Commented: (ZOOKEEPER-615) wrong javadoc for create with a sequence flag

[ https://issues.apache.org/jira/browse/ZOOKEEPER-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788818#action_12788818 ] Hadoop QA commented on ZOOKEEPER-615: - -1 overall. Here are the results of testing

[jira] Created: (ZOOKEEPER-617) improve cluster setup documentation in forrest

improve cluster setup documentation in forrest -- Key: ZOOKEEPER-617 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-617 Project: Zookeeper Issue Type: Bug Components: documentation

[jira] Commented: (ZOOKEEPER-458) connect_index in zookeeper handle might get out of bound.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1277#action_1277 ] Mahadev konar commented on ZOOKEEPER-458: - it still fails in the same place and

[jira] Created: (ZOOKEEPER-618) hudson not reporting failures correctly

hudson not reporting failures correctly --- Key: ZOOKEEPER-618 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-618 Project: Zookeeper Issue Type: Bug Components: tests Affects Versions:

[jira] Created: (ZOOKEEPER-619) hudson test failure in QuorumTest -- timeout error

hudson test failure in QuorumTest -- timeout error -- Key: ZOOKEEPER-619 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-619 Project: Zookeeper Issue Type: Bug Affects Versions: 3.3.0

[jira] Created: (ZOOKEEPER-620) hudson is not reporting compiler warning correctly

hudson is not reporting compiler warning correctly -- Key: ZOOKEEPER-620 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-620 Project: Zookeeper Issue Type: Bug Components: tests

[jira] Updated: (ZOOKEEPER-586) c client does not compile under cygwin

[ https://issues.apache.org/jira/browse/ZOOKEEPER-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-586: --- Attachment: ZOOKEEPER-586.patch this updated patch fixes (in addition to prev) the zkServe

[jira] Assigned: (ZOOKEEPER-586) c client does not compile under cygwin

[ https://issues.apache.org/jira/browse/ZOOKEEPER-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-586: -- Assignee: Patrick Hunt > c client does not compile under cygwin > --

Hudson build is back to normal: ZooKeeper-trunk #615

See

Re: [VOTE] Release ZooKeeper 3.2.2 (candidate 1)

+1 Ran Java and Python tests on OS X 10.6 and RHEL5, all pass. (I did discover that the Python tests don't run on Python 2.4 due to the use of 'all', but this is not something that needs fixing for the release). On Wed, Dec 9, 2009 at 9:18 PM, stack wrote: > +1 > > Put it under hbase and ran a

[jira] Commented: (ZOOKEEPER-458) connect_index in zookeeper handle might get out of bound.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789055#action_12789055 ] Steven Cheng commented on ZOOKEEPER-458: I'm out of ideas for now, can't find an

[jira] Commented: (ZOOKEEPER-458) connect_index in zookeeper handle might get out of bound.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789070#action_12789070 ] Mahadev konar commented on ZOOKEEPER-458: - I tried increasing the timer on waitF

[jira] Commented: (ZOOKEEPER-458) connect_index in zookeeper handle might get out of bound.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789148#action_12789148 ] Steven Cheng commented on ZOOKEEPER-458: Hmm.. I tried with a lower timeout on m