comparison mercurial/fancyopts.py @ 20883:cd443c7589cc

fncache: move fncache writing to be in a transaction Previously the fncache was written at lock.release time. This meant it was not tracked by a transaction, and if an error occurred during the fncache write it would fail to update the fncache, but would not rollback the transaction, resulting in an fncache that was not in sync with the files on disk (which causes verify to fail, and causes streaming clones to not copy all the revlogs). This uses the new transaction backup mechanism to make the fncache transacted. It also moves the fncache from being written at lock.release time, to being written at transaction.close time.
author Durham Goode <durham@fb.com>
date Mon, 24 Mar 2014 15:42:13 -0700
parents 1e5b38a919dd
children 753af9ee7c81
comparison
equal deleted inserted replaced
20882:5dffd06f1e50 20883:cd443c7589cc