[
https://issues.apache.org/jira/browse/IGNITE-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142707#comment-15142707
]
ASF GitHub Bot commented on IGNITE-2625:
----------------------------------------
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/474
IGNITE-2625 .NET: Fix field offset calculation in BinaryReader
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-2625
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/474.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 #474
----
commit e9692aa843862f2c69aaaf5cf51eaa46bca0af57
Author: Pavel Tupitsyn <[email protected]>
Date: 2016-02-11T13:18:55Z
IGNITE-2625 .NET: Fix field offset calculation in BinaryReader
----
> .NET: Incorrect field offset calculation in BinaryReader
> --------------------------------------------------------
>
> Key: IGNITE-2625
> URL: https://issues.apache.org/jira/browse/IGNITE-2625
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Fix For: 1.6
>
>
> See BinaryReader.SeekField(string), position from _curSchemaMap is used as
> is, and does not take current object offset (_curPos) into account.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
