-
Notifications
You must be signed in to change notification settings - Fork 278
Remove URL normalisation #1686
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove URL normalisation #1686
Conversation
tuf/download.py is legacy code base, should not be touched. The other failures are all in test_updater_ng: my first guess would be the test setup is broken: maybe the test setup uses local file paths as URL parts. |
c9440dc
to
ad7feb4
Compare
Pull Request Test Coverage Report for Build 1490229889Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
6da61b6
to
3407881
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really dislike hard coding OS specific path separators even in test code... but it looks like not doing that would mean we'd have to make the test infrastructure simpler, which is likely a bigger task and requires more infrastructure context.
So... maybe we take this as a win (removing hard coded OS specific path separators from actual library is still a big improvement, even if we just move them to tests), and move on.
@sechkova mind having a look, any opinions?
I agree with you, I'm ok with changing the tests like this for now. I only have one comment about |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
marking "request changes" for @sechkovas basename finding: leave a comment if it turns out to be actually necessary
As a target path is a URL path it's not correct to consider it as interchangeable with a filepath within every operation system. The unquote is also removed as the ngclient cannot assume correctly which encoding is intended and which not Fixes theupdateframework#1483 Signed-off-by: Ivana Atanasova <iyovcheva@iyovcheva-a02.vmware.com>
3407881
to
aa59192
Compare
Thanks! |
As a target path is a URL path it's not correct to consider it as
interchangeable with a filepath within every operation system. The
unquote is also removed as the ngclient cannot assume correctly
which encoding is intended and which not
Fixes #1483