This repository was archived by the owner on Aug 15, 2024. It is now read-only.
Bug When Reading Stream Backwards - #120
Merged
Merged
Conversation
thefringeninja
force-pushed
the
range-of-out
branch
2 times, most recently
from
May 2, 2018 12:06
368f7a3 to
3647138
Compare
thefringeninja
force-pushed
the
range-of-out
branch
from
May 2, 2018 12:06
3647138 to
b1839e9
Compare
thefringeninja
changed the title
thefringeninja
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When you read a stream backwards starting at a version that's beyond the end of the stream, the behavior is different depending on the implementation. Works as expected for MSSQL but throws an
ArgumentOutOfRangeExceptionfor the In Memory implementation.