Do not map (leave as is) trailing / or \ in github URLs. - #7418
Merged
Conversation
Otherwise we would fail to clone (git would start asking for password since there is no such repo) github repositories while including trailing / which should be perfectly fine and which git handles just fine: ❯ datalad -l debug clone https://github.com/datasets-mila/datasets--robotcar/ [DEBUG ] Command line args 1st pass for DataLad 0.18.4+21.g560dc910e. Parsed: Namespace() Unparsed: ['clone', 'https://github.com/datasets-mila/datasets--robotcar/'] [DEBUG ] Building doc for <class 'datalad.core.distributed.clone.Clone'> [DEBUG ] Parsing known args among ['/home/yoh/proj/datalad/datalad-maint/venvs/dev3/bin/datalad', '-l', 'debug', 'clone', 'https://github.com/datasets-mila/datasets--robotcar/'] [DEBUG ] Determined class of decorated function: <class 'datalad.core.distributed.clone.Clone'> [DEBUG ] Determined clone target path from source [DEBUG ] Resolved clone target path to: '/tmp/datasets--robotcar' [DEBUG ] Apply ephemeral patch to clone.py:_pre_annex_init_processing_ [DEBUG ] Apply ephemeral patch to clone.py:_post_annex_init_processing_ [DEBUG ] Apply RIA patch to clone.py:_post_git_init_processing_ [DEBUG ] Apply RIA patch to clone.py:_pre_final_processing_ [DEBUG ] URL substitution: 'https://github.com/datasets-mila/datasets--robotcar/' -> 'https://github.com/datasets-mila/datasets--robotcar-' [DEBUG ] Git clone from https://github.com/datasets-mila/datasets--robotcar- to /tmp/datasets--robotcar [DEBUG ] Run ['git', '-c', 'diff.ignoreSubmodules=none', 'clone', '--progress', 'https://github.com/datasets-mila/datasets--robotcar-', '/tmp/datasets--robotcar'] (protocol_class=GitProgress) (cwd=None) [DEBUG ] Non-progress stderr: b"Cloning into '/tmp/datasets--robotcar'...\n" Cloning: 50%|███████████████████████████████████████████████ | 1.00/2.00 [00:00<00:00, 534 candidates/s]Username for 'https://github.com': The fix consists of adding negative lookahead that the final (back)slash is not at the end of the string. I was not sure why (how do we get one) we are to map any backslash so did not introduce any special handling for it, so it just follows the same rule -- the last one would not be mapped.
mih
approved these changes
Jun 9, 2023
mih
left a comment
Member
There was a problem hiding this comment.
Makes sense. Thx for the detailed commit message, much appreciated!
Member
Author
|
appveyour on mac unrelated afaik |
Collaborator
|
PR released in |
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 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.
Otherwise we would fail to clone (git would start asking for password since there is no such repo) github repositories while including trailing / which should be perfectly fine and which git handles just fine:
The fix consists of adding negative lookahead that the final (back)slash is not at the end of the string. I was not sure why (how do we get one) we are to map any backslash so did not introduce any special handling for it, so it just follows the same rule -- the last one would not be mapped.