You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@fluo.apache.org by GitBox <gi...@apache.org> on 2018/05/27 16:49:04 UTC

[GitHub] kpm1985 commented on issue #1000: CuratorFramework and IntegrationTest Exceptions

kpm1985 commented on issue #1000: CuratorFramework and IntegrationTest Exceptions
URL: https://github.com/apache/fluo/issues/1000#issuecomment-392346652
 
 
   Hello guys, following back up on this I have successfully used Curator 2.12
   which has a lot of bugs fixed.
   
   I think it sounds reasonable to upgrade to this version as it was as simple
   as editing the pom. No new errors are created.
   
   However, as feared, it does not fix the issue. But it does upgrade and fix
   a lot of bugs in the dependency.
   
   On Mon, Apr 9, 2018, 2:24 PM Kenneth Mcfarland <ke...@apache.org>
   wrote:
   
   > Ok I will try a clean upgrade and then apply my logic to a patch if
   > necessary. Thank you Christopher.
   >
   > On Mon, Apr 9, 2018, 2:11 PM Christopher Tubbs <no...@github.com>
   > wrote:
   >
   >> Probably both. I think an updated curator would be reasonable, but it may
   >> not fix the problem.
   >>
   >> —
   >> You are receiving this because you authored the thread.
   >> Reply to this email directly, view it on GitHub
   >> <https://github.com/apache/fluo/issues/1000#issuecomment-379895453>, or mute
   >> the thread
   >> <https://github.com/notifications/unsubscribe-auth/Acg-LBdcuuoqGdIa1YHXDI_Re1gmlVVDks5tm86FgaJpZM4Rcl17>
   >> .
   >>
   >
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services