-
Notifications
You must be signed in to change notification settings - Fork 23
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
Misleading message "cannot find" #42
Comments
Logging happens sequentially. Here, an "expected" seed file (read from the The only thing to do here is improve/refine the first log message, i.e., add |
May be obvious to its developer, but not to a mere user like me... your explanation makes sense (exactly what I had figured out) but still initially I was puzzled what was going on. So yes, a clearer message would be good (e.g., "Pre-existing file <...> not found at <...>"). |
The "triggering full download" always makes me press Ctrl-C at that point. It is not only misleading but plain wrong, as one can see a few lines further down below. |
Here the message
is misleading. It took me a while to understand that after this message appears it still finds the seed file:
Hence, the first message should be changed to say "Could not find pre-existing original..." or something like that. Or the message should not appear at all if at least one seed file is given.
The text was updated successfully, but these errors were encountered: