Issue 2002: darcs saves files in caches even if it gets hash failures

Title	darcs saves files in caches even if it gets hash failures
Priority	bug	Status	given-up
Milestone		Resolved in
Superseder		Nosy List	dmitry.kurochkin, kowey
Assigned To		Topics	Hashed

Created on 2010-11-23.10:14:04 by kowey, last changed 2017-07-31.00:09:01 by gh.

msg13226 (view)

Author: kowey

Date: 2010-11-23.10:14:03

I'm pretty sure we can (need-action:) reproduce this fairly reliably by 
creating some kind of situation that would cause darcs to "download" a 
hash-mismatch file.

From personal experience and also from issue2000 (or maybe issue1993), I 
get the impression that darcs will (1) save files to cache and (2) check 
the hash.  If step 2 fails, the bad files are still left behind in the 
caches, which messes up further attempts at fetching a repository.

Shouldn't Darcs clean the bad files from the caches, or maybe just check 
first before saving them?

History
Date	User	Action	Args
2010-11-23 10:14:04	kowey	create
2017-07-31 00:09:01	gh	set	status: needs-reproduction -> given-up

Issue 2002 darcs saves files in caches even if it gets hash failures