curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cammckenzie <>
Subject [GitHub] curator issue #213: [CURATOR-395] Potential null dereference in PersistentNo...
Date Mon, 17 Apr 2017 23:57:59 GMT
Github user cammckenzie commented on the issue:
    Ah, I see now. It's the Preconditions.checkState call that causes the issue. I thought
that we could just hold a reference to the builder and then call forPath() on it when required.
But that checkState call will fail if the client is not started.
    So, the PR looks OK to me. Merge away.

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 enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message