Sometimes, a version control operation tried by Crystal fails, or produces
output to standard error.
1. If the output is only to standard error, and the exit status is OK, then
does the user really need to be informed? (I'm not sure what all the cases
are; it would be good for you to collect logs and find out all such
occurrences.)
2. Right now, the user is given two options:
* ignore the repository
* re-clone
2.1. I am not sure that the "ignore" option really ignores; even though I
always choose that, I haven't seen the red X in a very long time.
2.2. There is not a "retry" option. But, I frequently get transient
errors. For example, suppose that Dropbox is in the middle of coping
changes from a remote repository to my local Dropbox copy. Then, the
Mercurial repository may temporarily be in an inconsistent state. Trying
again immediately or after a short wait would probably result in success,
without any need to distract the user.
Original issue reported on code.google.com by yuriy.b...@gmail.com on 13 Jul 2011 at 2:32
Original issue reported on code.google.com by
yuriy.b...@gmail.comon 13 Jul 2011 at 2:32