Issue 2134: applyHashed catches any exceptions, leading to attempted repo conversion

Title	applyHashed catches any exceptions, leading to attempted repo conversion
Priority		Status	given-up
Milestone		Resolved in
Superseder		Nosy List	owst
Assigned To	owst	Topics

Created on 2012-01-19.11:16:58 by owst, last changed 2017-07-31.00:49:13 by gh.

msg15039 (view)

Author: owst

Date: 2012-01-19.11:16:58

Noticed in Issue2133; when a patch fails to apply, the Prelude.catch in
applyHashed (src/Darcs/Repository/HashedRepo.hs) catches the exception,
leading to an unnecessary (and misleading) "Doing a one-time conversion"
message. 

We should ensure that we only perform a conversion if we know we need to
(probably some specific exceptions needed, but I've not really thought
about where other exceptions are coming from, and in what instances we
want to convert).

History
Date	User	Action	Args
2012-01-19 11:16:58	owst	create
2012-10-16 10:27:21	owst	set	assignedto: owst
2017-07-31 00:49:13	gh	set	status: unknown -> given-up

Issue 2134 applyHashed catches any exceptions, leading to attempted repo conversion