mirrors/arti.git/crates/tor-persist/src/testing.rs, branch arti-v1.1.0

add feature annotation not added by doc_auto_cfg

2022-08-24T16:22:41Z

tor-persist: Big refactoring on Error type.

2022-07-06T15:47:17Z

Every error now has an action (what we were trying to do), a resource (what we were trying to do it to), and a source (what problem we encountered). Initially I tried to add "action" and "resource" fields to error variants individually, but that led to a combinatorial explosion. Part of #323.

tor-persist: Move Error to a module.

2022-07-06T10:38:10Z

Fix clippy::significant_drop_in_scrutinee warnings

2022-06-15T15:52:30Z

This is apparently a new warning from clippy nightly, documented in https://rust-lang.github.io/rust-clippy/master/index.html#significant_drop_in_scrutinee . I'm not in love with the temporary variables that this warning wants me to introduce, but it does seem like a decent way to avoid some kinds of deadlock.

arti-client: Unlock the state manager on failure to bootstrap

2022-02-24T19:55:59Z

`StateMgr` got a new `unlock()` method that does what it says on the tin. We now call it from `bootstrap()` using the new `util::StateMgrUnlockGuard`, which works in a manner similar to the `BoolResetter` from `tor_dirmgr`. (A decent small little task in future might be to unify these types in some sort of general arti utility crate?) closes arti#335

tor-persist: Distinguish load vs. store json errors

2022-02-04T14:33:09Z

Serialisation errors ought not to occur, since they would represent an attempt to store malformed data, or something. (We always convert to a string, so the JSON error never contains IO errors or the like.) Deserialisation errors mean the persistent state is corrupt.

address clippy's latest lint

2021-12-20T09:46:41Z

Change how TestingStateMgr handles locking.

2021-11-03T17:27:01Z

Previously it was either all-locked or all-not-locked. Now you can simulate having the same shared storage opened by multiple managers, only one of which has the lock.

Add Futureproof wrapper type, use for GuardDisabled enum

2021-10-27T14:10:44Z

The Futureproof type lets you serialize and deserialize types whose representations might change (most useful for enums that might grow additional variants). It uses #[serde(untagged)] to accomplish this. This gets used in order to make the `disabled` field of `Guard` more robust against future guard disablement reasons being added. A test was also added to verify correct behaviour of the new type.

Remove try_lock from StorageHandle.

2021-10-20T13:42:34Z