[
https://issues.apache.org/jira/browse/STORM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14201816#comment-14201816
]
Sean T Allen commented on STORM-549:
found the bug. the problem is this line
I find the source of the problem. The config value is a java boolean
And (not (Boolean. false)) == false
So the value is effectively ignored.
See last comment on the ticket at:
https://issues.apache.org/jira/browse/STORM-549
Can I just open a PR again the github repo with the fix for this?
On
[
https://issues.apache.org/jira/browse/STORM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14201826#comment-14201826
]
Jungtaek Lim commented on STORM-549:
Oh, I didn't ever think about it. It's hell of
[
https://issues.apache.org/jira/browse/STORM-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202123#comment-14202123
]
Sean Zhong commented on STORM-492:
--
Sorry for the mistake.
Test timeout should be
[
https://issues.apache.org/jira/browse/STORM-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202139#comment-14202139
]
Jungtaek Lim commented on STORM-492:
No, not at all. It's just a reminder. Thanks for
This is a call to vote on adopting the proposed bylaws (attached below) as the
bylaws for the Apache Storm project.
For convenience, a rendered version of the markdown can be found here:
https://github.com/apache/storm/blob/fdbc5ebd081b6b8d6ed4da595ce6f0025343d0ee/BYLAWS.md
This vote will be
On Fri, Nov 7, 2014 at 2:54 PM, P. Taylor Goetz ptgo...@apache.org wrote:
Membership of the PMC is by invitation only and must be approved by a
consensus approval of active PMC members. A PMC member is considered
emeritus by their own declaration or by not contributing in any form
to the
[
https://issues.apache.org/jira/browse/STORM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
P. Taylor Goetz updated STORM-549:
--
Fix Version/s: 0.9.3-rc2
topology.enable.message.timeouts does nothing
[
https://issues.apache.org/jira/browse/STORM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14202763#comment-14202763
]
P. Taylor Goetz commented on STORM-549:
---
[~SeanTAllen], thanks for your efforts in
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/306#issuecomment-6089
+1
---
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
Some comments inline:
On Fri, Nov 7, 2014 at 12:54 PM, P. Taylor Goetz ptgo...@apache.org wrote:
This is a call to vote on adopting the proposed bylaws (attached below) as
the bylaws for the Apache Storm project.
For convenience, a rendered version of the markdown can be found here:
Just to set some context here, we already had an earlier discussion that is
relevant:
http://mail-archives.apache.org/mod_mbox/storm-dev/201406.mbox/%3ccadmkjezy9bwbcmw-zg2z97js8afyn++483vxlueq18agmw7...@mail.gmail.com%3e
Suresh brings up a good point with respect to feature branches (like the
security branch).
We should have a provision for working in a feature branch within the Apache
repo with fewer restrictions. Without that, we are encouraging developers to
collaborate outside of Apache (I.e. p2p github
Well sorry to have missed the previous discussion thread but I really think
that the consensus voting provisions are serious problems. It would have been
much better for me to raise these issues earlier. My apologies for not doing
so.
-1 for the record as this proposal stands.
My own
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/306#issuecomment-62243796
@strongh thanks for patch. Can we make this into a utils.clj function .
Similar code is used in supervisor.clj too.
---
If your project is set up for it, you can reply
15 matches
Mail list logo
