curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hdeadman <>
Subject [GitHub] curator pull request: CURATOR-157 Avoid stack traces on close
Date Tue, 19 Jan 2016 23:43:23 GMT
Github user hdeadman commented on the pull request:
    What's the status on this pull request? It looks like @bdumon added a test. Is the issue
that there are branch conflicts? Does the error not happen in 3.0? I am getting it on 2.9.1
if I use a try block that relies on the Closable interface. 

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