Github user Randgalt commented on the issue:
https://github.com/apache/curator/pull/216
I'll look at this soon. This needs to be addressed once and for all.
---
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
Github user lvfangmin commented on the issue:
https://github.com/apache/curator/pull/216
This fix looks good to time, but I'd like @Randgalt to accept it since he
has more context about the changes he made in CURATOR-345.
---
If your project is set up for it, you can reply to this
