Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
From: epollan <git@git.apache.org>
To: dev@curator.apache.org
Reply-To: dev@curator.apache.org
Message-ID: <git-pr-168-curator@git.apache.org>
Subject: [GitHub] curator pull request #168: CURATOR-354: native memory leak in GzipCompressio...
Content-Type: text/plain
Date: Thu,  6 Oct 2016 21:15:58 +0000 (UTC)
archived-at: Thu, 06 Oct 2016 21:16:01 -0000

GitHub user epollan opened a pull request:

    https://github.com/apache/curator/pull/168

    CURATOR-354: native memory leak in GzipCompressionProvider

    explicitly close GZIP input/output streams in GzipCompressionProvider

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/epollan/curator CURATOR-354

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/168.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #168
    
----
commit 8c1b4be57ffaf58ce8708e0e9d3611e4e5955f2e
Author: Evan Pollan <evan.pollan@gmail.com>
Date:   2016-10-06T20:53:04Z

    CURATOR-354: explicitly close GZIP input/output streams in GzipCompressionProvider

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---