mirrors/arti.git/crates/tor-persist/src/fs.rs, branch derive-traitsmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=derive-traits2022-02-24T19:55:59Zarti-client: Unlock the state manager on failure to bootstrap2022-02-24T19:55:59Zetator@eta.st2022-02-18T16:02:18Zurn:sha1:c6fdd7c0037df821a7cfc475993322958c2f006a
`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 errors2022-02-04T14:33:09ZIan Jacksonijackson@chiark.greenend.org.uk2022-01-13T16:50:14Zurn:sha1:a4765717da64cc287f09e429989c79b97d794ded
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.
clippy: Pass simply &output to fs::write2022-02-02T18:33:23ZIan Jacksonijackson@chiark.greenend.org.uk2022-02-02T17:52:07Zurn:sha1:b695ebd039fd71af75beb1d7685f5b54138dec31
clippy::needless_borrow quibbles here, IMO correctly. Its suggestion
didn't go far enough: output is a String and a &String can be passed
to write as-is for identical effect.
Fix Rustdoc errors.2021-12-08T15:06:22ZNick Mathewsonnickm@torproject.org2021-12-08T15:06:22Zurn:sha1:9767a1d063491434e75689478e268373c3e11310Test FsStateMgr::path(), and fix a bug in it.2021-12-08T01:11:54ZNick Mathewsonnickm@torproject.org2021-12-08T01:11:54Zurn:sha1:327d485b17344f6842267305978dbaa4d2dfcfdb
We join "state" to the directory name, so we must call parent() to get
the original.
Sketch API for reconfiguration.2021-12-07T20:42:14ZNick Mathewsonnickm@torproject.org2021-12-06T18:54:53Zurn:sha1:606d64eac5936a9f0bfec32b8b5a85f3dea77559
This patch doesn't actually make anything reconfigurable, but it
does create an API that will tell you "you can't change the value of
that!" If the API looks reasonable, I can start making it possible
to change the values of individual items.
Upgrade to fslock version 0.22021-10-27T18:52:09ZNick Mathewsonnickm@torproject.org2021-10-27T18:52:09Zurn:sha1:2fae63b5aea73f816df96cb2db53eba6ac5f89bb
This version makes all locks per-handle rather than per-process, by
moving from lockf() to flock() on unix.
Replace the return type of StorageMgr::try_lock with a tristate2021-10-20T13:37:53ZNick Mathewsonnickm@torproject.org2021-10-20T13:37:53Zurn:sha1:7b6ed9dab6a673b9b563fa3818806cec4b208240
It's useful to know now only if we now have the lock, but also if we
just got it for the first time.
Change tor-persist to use json instead of toml.2021-10-07T13:30:08ZNick Mathewsonnickm@torproject.org2021-10-07T13:23:35Zurn:sha1:7e68883a27c59b770022484626730e5b89b9587e
The limitations with toml seemed to be reaching a head, and I wasn't
able to refactor the guardmgr code enough to actually have its state
be serializable as toml. Json's limitations are much narrower.
Move FsStatemgr to an inner module.2021-09-30T19:36:11ZNick Mathewsonnickm@torproject.org2021-09-30T15:04:19Zurn:sha1:eef06efea666c9bac1d51acc4e5f07168e205aa3