mirrors/arti.git/crates/tor-persist/src/fs.rs, branch arti-v1.8.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.02025-11-06T11:28:22ZFix name of clippy lint to unchecked_time_subtraction (2)2025-11-06T11:28:22ZIan Jacksonijackson@chiark.greenend.org.uk2025-11-06T11:23:25Zurn:sha1:a5fd5c48ea059a80cc1f6c50e248654b5ff3aaff
Run maint/add_warning
Switch Cargo.toml files to edition 2024.2025-08-07T15:28:36ZNick Mathewsonnickm@torproject.org2025-08-06T01:19:58Zurn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc
First, run
```
git grep -l "^edition =" |
xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```
Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.
Third, run cargo fmt again.
Update code for Edition 20242025-08-07T15:28:31ZNick Mathewsonnickm@torproject.org2025-08-07T12:44:47Zurn:sha1:0453fb4be8cf618b94230812957ce1db1afe74bd
1. Run cargo fix --edition
2. Selectively revert the "if let"->"match" changes.
These changes are meant to protect us from the lifetime changes
for "if let" bindings in Rust 2024.
But we're not actually relying on the old lifetime rules
anywhere, and the match syntax here is quite ugly.
3. Automatically revert `$pat:expr_2021` to `$pat:expr`.
(We don't actually want to restrict the expression syntax
that our macros accept).
Done with
`git grep -l expr_2021 | xargs perl -i -pe 's/expr_2021/expr/g;'`
4. Run cargo fmt.
tor-persist: miri: disable tests that involve fs access2024-10-08T15:53:28ZIan Jacksonijackson@chiark.greenend.org.uk2024-10-07T12:14:27Zurn:sha1:9e9ab427948a3b7fed7b19b17715c4d67fda9682extract tor_async_utils::oneshot into ::oneshot-fused-workaround2024-08-28T14:27:46ZJim Newsomejnewsome@torproject.org2024-08-22T19:20:36Zurn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1
Having this in the `tor-async-utils` crate prevents us from doing both
of the following without introducing a circular dependency:
* using it in `tor-rtmock` (which we currently do, particularly in
tests).
* using `tor-rtmock` to test things in `tor-async-utils`. We don't do
this yet, but it is generally sensible to do so. In particular we
want to move the `stream_peak` module there, which is currently tested
with `tor-rtmock`.
Moving this into its own crate avoids this circular dependency.
implement TorClient::wait_for_stop2024-07-11T16:02:18Ztrinity-1686atrinity@deuxfleurs.fr2024-06-02T08:38:16Zurn:sha1:9e0afcdcab0be86d1a18b99d7bb4bc6b24998a3dFix clippy::doc_lazy_continuation2024-07-08T10:36:25ZIan Jacksonijackson@chiark.greenend.org.uk2024-07-08T10:31:47Zurn:sha1:c4fe208c7184c020b5418840ebc5f4044c1601c6Run maint/add_warning.2024-03-13T16:30:53ZNick Mathewsonnickm@torproject.org2024-03-13T16:30:53Zurn:sha1:c0c9bd15d42897825dd0ab3d3b8dd1c17bd6320ctor-persist: Improve test portability2024-03-01T12:56:54ZTobias Stoeckmanntobias@stoeckmann.org2024-03-01T10:51:14Zurn:sha1:0f882658e2bf2d4fc218de559871be812f8c6951
The test fails on Windows systems for two reasons:
- File separator \ is printed in error message instead of expected /
- Temporary files are located within home directory, which is anonymized
Test failure can be provoked on Linux as well by setting TMPDIR to point
to a directory within HOME.
tor-persist: Provide load_store module for use by state_dir2024-01-24T16:29:19ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-24T11:45:04Zurn:sha1:d2d1cc31f76c20c165a5c16cbc774b0e0f6d9297