reimplement #373 to work on Windows #384
Merged
Conversation
This file contains 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
This ensures no file handles are left open after receiving an unsatisfiable range request by never opening the stream in the first place.
kherock
force-pushed
the
fix-range-requests-windows
branch
from
06a57cc to
0e77615
Compare
|
Solid refactor @kherock excellent work! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This ensures no file handles are left open after receiving an unsatisfiable range request by never opening the stream in the first place.
Also I found that on my end, the value reported by
fs.ReadStream#byteReadwas often 0 bytes since I'm guessing that value only reflects what has been lazily read.