-
Notifications
You must be signed in to change notification settings - Fork 33
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
client crash on copying non empty directory #105
Comments
Will check next.
It should not, there is some defence against crashes in the linker. If the state got broken that is a separate bug.
I guess we can do a |
Note that staging to non existing dir works, i.e.
Which deviates from standard shell |
Still digging the top most bug description with recursive copy, apparently we have a problem when a directory copied inside of another directory. Looks like Quick questions: how content of the directory is calculated? Is it based on names of the children or their content? Also, am I right that Also, |
IIRC the logic for
It's only based on the directory path, no content involved.
That would only serve as key for one version of that file.
Partly yes, It trades storage against CPU. On |
Steps to reproduce: start fresh and do
I just show first line of the crash report. Depending on what inside of the parent dir (I think it subdirs), the repo database could be left in a broken state.
While we at it, it would be nice to be able to copy to non-existing path. For example, in above to do
ali cp /test/dir1 /to/new/non/existing/dir
The text was updated successfully, but these errors were encountered: