1. Summarise the issue (what were doing, what went wrong?)
this is two apostrophes with nothing between them
$ darcs diff ''
darcs failed: Unexpected failure in updateIndex!
2. What behaviour were you expecting instead?
No failure!
3. What darcs version are you using? (Try: darcs --exact-version)
2.9.5
4. What operating system are you running?
Ubuntu X86_64
I triggered the same issue with darcs 2.9.6, by running "darcs whatsnew" on a
non-existent file path:
$ darcs w /perllib/Role/REST/
Ignoring non-repository paths: /perllib/Role/REST/
Why would either of these operations trigger an index update anyway, since
neither modifies data? That seems like a pessimization.
It's a bit of a tricky question, whether read-only commands should update
caches like the [file] index and the patch index. I think they probably
should, but they need to be tolerant of failure.
priority: bug status: unknown -> needs-testcase messages:
+ msg16616 title: darcs diff && darcs whatnews can fail with " Unexpected failure in updateIndex! " when they perform no action -> diff/whatsnew: Unexpected failure in updateIndex! when they perform no action