mirrors/arti.git/crates/fs-mistrust, branch arti-v1.1.7mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.72023-08-01T14:57:55ZIncrement patchlevel versions of crates with minor changes2023-08-01T14:57:55ZNick Mathewsonnickm@torproject.org2023-08-01T14:57:55Zurn:sha1:3acdf102c705314aec63679e97240bb7d981d1c8
These crates are at version 0.x.y, so we don't need to distinguish
new-feature changes from other changes:
```
tor-basic-utils
fs-mistrust
tor-error
tor-geoip
tor-checkable
tor-linkspec
tor-netdoc
tor-netdir
tor-persist
tor-ptmgr
tor-hsservice
```
This crate has a breaking change, but only when the semver-breaking
feature `experimental-api` is enabled:
```
tor-config
```
This crate is at version 1.x.y, but has no new public APIs, and
therefore does not need a minor version bump:
```
arti
```
Run cargo +nightly fmt to format many let ... else ...2023-07-24T12:46:05ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-24T12:46:05Zurn:sha1:3e2a909707acf7cad2621316a51f8643f1fe908a
rustfmt has grown opinions about how let ... else ... ought to be
formatted. They don't always agree with our previous manual
decisions.
I think our policy is to always insist on rustfmt. When that version
of rustfmt hits stable, our CI will start to fail for everyone.
(Right now this discrepancy just causes trouble for contributors who
are using nightly by default.)
Update pwd-grp to 0.1.1 to fix MacOS build etc.2023-07-20T17:58:02ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-20T17:56:18Zurn:sha1:1f7911f0d9084b9c2f6c7909a924d4c2e23db09e
This also gets rid of a duplicate copy of derive-adhoc.
fs-mistrust: Run rustfmt to apply deferred formatting churn2023-07-14T15:02:45ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-14T14:10:37Zurn:sha1:967a36ee424aed0b0dbe216536990e7437e6b3a3fs-mistrust: In a test, simplify env var handling2023-07-14T15:02:45ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-14T14:06:18Zurn:sha1:f137cbbe7c4e1d660685934a53027956cb5120a2fs-mistrust: users: Use OsStr and OsString a lot less2023-07-14T15:02:45ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-14T14:01:48Zurn:sha1:792371a68867a27ad22cc473c613c9402b6c73c3
We don't use OsString now except where it appears in our public API,
or where we get it from std::env.
Moving the `use` statements into the use sites enabled me to see
that I had found all the places I wanted to change.
fs-mistrust: Remove a now-unneeded suppression2023-07-14T15:02:45ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-14T13:46:43Zurn:sha1:5f3571fdf3e4c4dc732dec05453e15ef3ce06ed7
This function is actually (properly) fallible now.
fs-mistrust: forbid unsafe code2023-07-14T15:02:45ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-14T12:13:53Zurn:sha1:41543b06d67e55846cabe2ae773476510515227dfs-mistrust: Replace a direct libc call in a test2023-07-14T15:02:45ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-14T12:13:42Zurn:sha1:c943f734d69087952b79ce666e1081b5e917ff56fs-mistruct: Abolish some now-unneeded muts2023-07-14T15:02:45ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-14T11:13:12Zurn:sha1:e4bb7c388ae461e047af4ff9aa5d93f7f9942a7b
MockPwdGrpProvider has internal mutability and is Sync, so its add
functions take &self.