[GitHub] ignite pull request: IGNITE-1921 .Net: Handle leak during ComputeJ...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request: IGNITE-1921 .Net: Handle leak during ComputeJ...

andrey-kuznetsov
GitHub user ptupitsyn opened a pull request:

    https://github.com/apache/ignite/pull/236

    IGNITE-1921 .Net: Handle leak during ComputeJobHolder serialization

   

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

    $ git pull https://github.com/ptupitsyn/ignite ignite-1921

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

    https://github.com/apache/ignite/pull/236.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 #236
   
----
commit 31e001010ee4352ef5913fd3c1619789a599d358
Author: Pavel Tupitsyn <[hidden email]>
Date:   2015-11-16T10:17:38Z

    IGNITE-1921 .Net: Handle leak during ComputeJobHolder serialization

commit 989d2d9e617d4e0f1aa5dc59feddb8001ea64513
Author: Pavel Tupitsyn <[hidden email]>
Date:   2015-11-16T10:28:27Z

    Fix ComputeTaskHolder

commit 89a068b37c026c3045e6e9bd4670ff96ef242a22
Author: Pavel Tupitsyn <[hidden email]>
Date:   2015-11-16T10:40:44Z

    Add tests

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #236: IGNITE-1921 .Net: Handle leak during ComputeJobHol...

andrey-kuznetsov
Github user ptupitsyn closed the pull request at:

    https://github.com/apache/ignite/pull/236


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---