FileRangeReader Improved URI Handeling #3034
Merged
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.
Overview
This PR fixes a bug in
FileRangeReaderProvider
where it was unable to process certainURI
s. Looking into the issue, I found the cause of the problem to be with how we were converting URIs to Files. It turns out thatPaths.get
has certain restrictions on how theURI
has to be formatted. These differ from theURI
specification, and can sometimes cause properly formattedURI
s to be denied.What I ended up deciding on was to simply pass in a
String
toPaths.get
in order to get around the differentURI
requirements. To do that, I first check to see if the givenURI
had ascheme
or not. If it doesn't then I just convert it to aString
. Otherwise, I strip the scheme from the path and then pass in the scheme-lessString
.Checklist
docs/CHANGELOG.rst
updated, if necessaryCloses #3031