##// END OF EJS Templates
tests: demonstrate a case where a corrupt tag cache causes an abort...
tests: demonstrate a case where a corrupt tag cache causes an abort I happened to hit this trying to cover other cases around valid vs missing entries. I have no idea if this is something that could occur more naturally (similar to how a missing file node in `hgtagsfnodes1` can occur after a strip). There is a test just above this added in f5a7cf0adb12 mentioning it "overwrites the junk", though that tests truncation instead of actual garbage. But since this is just a cache, it probably shouldn't abort with a cryptic message like this. The two options I see both have downsides- either rebuild the cache (and potentially take a long time), or hint to the user to run a debug command. Differential Revision: https://phab.mercurial-scm.org/D9812

File last commit:

r46136:b51167d7 default
r47400:9ea6b75b default
Show More
dirstate_tree.rs
14 lines | 398 B | application/rls-services+xml | RustLexer
// dirstate_tree.rs
//
// Copyright 2020, Raphaël Gomès <rgomes@octobus.net>
//
// This software may be used and distributed according to the terms of the
// GNU General Public License version 2 or any later version.
//! Special-case radix tree that matches a filesystem hierarchy for use in the
//! dirstate.
//! It has not been optimized at all yet.
pub mod iter;
pub mod node;
pub mod tree;