Skip to content
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

Modified Date and Size compare generates "Unable to compare files" when file size is 0 #260

Open
mach128x opened this issue Feb 1, 2020 · 1 comment

Comments

@mach128x
Copy link

mach128x commented Feb 1, 2020

When doing a Content compare, the "Unable to compare files" warning when file size is 0 makes sense.

However when choosing the "Modified Date and Size" compare method, I am not expecting the content to be compared but still get the warning on 0 size files. In that context the warning does not make sense as it does not even apply. For that reason I consider this to be a bug.

@sdottaka
Copy link
Member

I cannot reproduce this problem.
Normally, "Unable to compare files" does not appear when comparing 0-byte files using the "Modified Date and Size" method.

I suspect you are comparing very special folders. What folders are you comparing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants