git-svn: do not reuse caches memoized for a different architecture

Reusing cached data speeds up git-svn by quite a fair bit. However, if the YAML module is unavailable, the caches are written to disk in an architecture-dependent manner. That leads to problems when upgrading, say, from 32-bit to 64-bit Git for Windows. Let's just try to read those caches back if we detect the absence of the YAML module and the presence of the file, and delete the file if it could not be read back correctly. Note that the only way to catch the error when the memoized cache could not be read back is to put the call inside an `eval { ... }` block because it would die otherwise; the `eval` block should also return `1` in case of success explicitly since the function reading back the cached data does not return an appropriate value to test for success. This fixes https://github.com/git-for-windows/git/issues/233. [ew: import "retrieve" explictly, check unlink result] Signed-off-by: Gavin Lambert <github@mirality.co.nz> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Eric Wong <e@80x24.org>

Gavin Lambert committed Oct 25, 2016 at 17:30 UTC a2c761ce5b7a5fd8b505b036f3509a9e6617dee8
1 file changed +11 -1
perl/Git/SVN.pm
+11 -1
@@ -1658,7 +1658,17 @@ sub tie_for_persistent_memoization {
1658 if ($memo_backend > 0) {
1659 tie %$hash => 'Git::SVN::Memoize::YAML', "$path.yaml";
1660 } else {
1661 - tie %$hash => 'Memoize::Storable', "$path.db", 'nstore';
1661 + # first verify that any existing file can actually be loaded
1662 + # (it may have been saved by an incompatible version)
1663 + my $db = "$path.db";
1664 + if (-e $db) {
1665 + use Storable qw(retrieve);
1666 +
1667 + if (!eval { retrieve($db); 1 }) {
1668 + unlink $db or die "unlink $db failed: $!";
1669 + }
1670 + }
1671 + tie %$hash => 'Memoize::Storable', $db, 'nstore';
1672 }
1673 }
1674