-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
The Grand NoCopy Bug #5924
Comments
@DonaldTsang - Thanks for creating this meta issue. Upon further reading I'm not sure these issues are actually closely related. #4558 is a documentation (?) issue I guess and I think @magik6k explains why it exists and how to get the desired behavior here: #4558 (comment) #4224 is a feature request of sorts - although not super clear. There is a potential solution using symlinks, but it doesn't suit everyone's use case. #4318 is also I guess a documentation issue? The reason for this behavior is summarized here: #4318 (comment) and is discussed more in the issue. #5184 looks like a bug straight up. What is the problem that you are running into specifically? Is it #5184? The others are behaviors that are unlikely to change, although we could document them better. I'm tempted to close them and open up a separate issue that just covers documentation of that behavior. |
@eingenito the main issues are #4224 and #4558 in my case for Hydrus, which I hope there should be more documentation and research on the matter. |
I've created an issue to specifically track what needs to land for this feature to stabilize: #7161. |
Main issue: #4558 ("nocopy" option for "add" method doesn't work in a HTTP API call)
Secondary issue: #4224 (nocopy option doesnt work without moving files (defeating part of the purpose))
Third issue: #5815 (Recursive add of large directory fails at 100% (with nocopy and fscache))
Fourth issue: #4318 (nocopy adds files with different hashes than without nocopy)
Software that uses NoCopy (that I am aware of):
Software that could use NoCopy:
An odd solution referenced by a random forum:
Now all we need to do is to reproduce the bug
The text was updated successfully, but these errors were encountered: