- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 5
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
"Remote I/O error (121)" trying to delete a remote directory containg files. #4364
Comments
Branch: 4364_fish_remove_nonempty_dir |
I would add a comment to the source code referencing this ticket to explain why these checks are needed (that is for VFS support). Otherwise, someone will surely optimise it again a decade later ;-) |
I'll add a comment to the commit before merge: |
Well, I meant the source code, not the commit message. Surely you won't be blaming every line before considering whether to change it or not... |
when something seems obviously wrong, i actually tend to blame it to figure out whether i'm missing something. tough i suppose i may be somewhat exceptional in that regard.
code comments also have the unfortunate habit of going out of sync with reality, so their "cautionary" value tends to be limited in practice.
nonetheless, i agree that they should be added as a matter of best practice. |
|
Merged to master: [7bbaa13].
|
|
Important
This issue was migrated from Trac:
gv
(gabriel@….net)Description of the problem:
Most of the times I cannot delete directories that have files or others directories on a remote machine (I connect using cd sh://user@host/home/user). I get something like this:
For most of directories in /home/user it does not work. Occasionally, for some directories, it works. And I cannot find a pattern here.
The only workaround for this issue is to first manually remove files from the directory and then remove the directory itself. This is easy if the directory tree is small. But for sure not feasible for a large directory tree.
Steps to reproduce:
Thank you!
The text was updated successfully, but these errors were encountered: