-
Notifications
You must be signed in to change notification settings - Fork 393
fix(rsync,scp): remove file-type marks from "ls -F" properly #1398
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
Conversation
3227068
to
2e21621
Compare
test/t/test_scp.py
Outdated
assert_bash_exec(bash, "mkfifo '%s/local_path_1-pipe'" % tmpdir) | ||
except Exception: | ||
pytest.skip( | ||
"The present system does not allow creating a named pipe." |
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 wonder if there's a valid setup that would allow creating these, but just doesn't have mkfifo
installed. The end result would be the same, but the skip message would be misleading. Maybe include the stringified exception in it and generalize a bit, something like f"Could not create a named pipe: {ex}"
?
Pre-approved with this addressed some way.
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 wonder if there's a valid setup that would allow creating these, but just doesn't have
mkfifo
installed.
I anticipated the opposite situation, where mkfifo
is installed, yet creating a named pipe is not allowed. For example, MSYS 1.0 doesn't support creating a named pipe:
$ mkfifo a.pipe
mkfifo: cannot create fifo `a.pipe': Function not implemented
Although I haven't tried, I also wonder if we can create a named pipe inside a USB memory stick (whose filesystem is usually FAT32).
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.
With #1397 merged, is this in a draft state for some other reason, perhaps the above discussion?
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.
Sorry, I've simply been busy. I'll take a look again soon.
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 added a clarification in b3e01d6..bc07307
.
2e21621
to
b3e01d6
Compare
The type-classifier characters for named pipes (|) and sockets (=) were not properly removed. These are escaped by a backslash before removing, so the backslashes are left. In this patch, we remove the type-classifier characters before performing the backslash escaping.
b3e01d6
to
bc07307
Compare
I've merged this. |
This was a part of #1371 but was separated. Waiting for #1397.
Details are described in the commit message.