-
Notifications
You must be signed in to change notification settings - Fork 25
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
Confusing scenario #210
Comments
!!! Tarsnap shouldn't be able to have two archives names Can you go to the command-line and try:
and send the result to me by email? (assuming that you're sharing the key between gui and CLI) |
I've disallowed archive and job names that begin or end with whitespace, so this should avoid the confusion scenario. (I think it's better to stop people from creating such archives, instead of silently removing whitespace.) |
As a user, I experienced something quite confusing. I thought I'd better report it to be safe:
Result:
Why did Tarsnap fail to create two archives named "disruption", but it successfully created two archives named "disruption1"? I expected that Tarsnap would fail to create the second "disruption1" and was mildly shocked when it succeeded.
If it's expected that you should be able to create archives with identical names, then why did Tarsnap fail to create two archives named "disruption"?
The text was updated successfully, but these errors were encountered: