[GitHub] ignite pull request: ignite-1718 Fix of 'Not enough data to read t...

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

[GitHub] ignite pull request: ignite-1718 Fix of 'Not enough data to read t...

andrey-kuznetsov
GitHub user agura opened a pull request:

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

    ignite-1718 Fix of 'Not enough data to read the value' and 'No class definition for typeId: 0' in portable marshaller

   

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

    $ git pull https://github.com/agura/incubator-ignite ignite-1718

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

    https://github.com/apache/ignite/pull/165.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 #165
   
----
commit a1367ef226057989695c8e635eb9d5c51ccb1514
Author: agura <[hidden email]>
Date:   2015-10-19T13:31:27Z

    ignite-1718 Fix of 'Not enough data to read the value' and 'No class definition for typeId: 0' in portable marshaller

----


---
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: ignite-1718 Fix of 'Not enough data to read t...

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

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


---
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: ignite-1718 Fix of 'Not enough data to read t...

andrey-kuznetsov
In reply to this post by andrey-kuznetsov
GitHub user agura reopened a pull request:

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

    ignite-1718 Fix of 'Not enough data to read the value' and 'No class definition for typeId: 0' in portable marshaller

   

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

    $ git pull https://github.com/agura/incubator-ignite ignite-1718

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

    https://github.com/apache/ignite/pull/165.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 #165
   
----
commit a1367ef226057989695c8e635eb9d5c51ccb1514
Author: agura <[hidden email]>
Date:   2015-10-19T13:31:27Z

    ignite-1718 Fix of 'Not enough data to read the value' and 'No class definition for typeId: 0' in portable marshaller

commit 542ee46c0d53f7be0300ce983ec4726b6f4aa85f
Author: agura <[hidden email]>
Date:   2015-10-20T14:50:45Z

    ignite-1718 Fix of 'Not enough data to read the value' and 'No class definition for typeId: 0' in portable marshaller

----


---
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: ignite-1718 Fix of 'Not enough data to read t...

andrey-kuznetsov
In reply to this post by andrey-kuznetsov
Github user agura closed the pull request at:

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


---
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.
---