mirrors/arti.git/crates/tor-rtmock, branch arti-v1.1.8mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.82023-09-05T16:22:19ZUpdate patchlevel for crates with nontrivial changes.2023-09-05T16:22:19ZNick Mathewsonnickm@torproject.org2023-09-05T16:22:19Zurn:sha1:e251baa9a77415f3c605ff462a8ac0b3fa37660a
These are:
```
hashx
equix
tor-async-utils
tor-error
tor-config
tor-rtmock
tor-llcrypto
tor-bytes
tor-hscrypto
tor-hspow
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-chanmgr
tor-guardmgr
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
arti-client
arti
```
Merge branch 'clippy' into 'main'2023-08-23T13:24:18ZIan Jacksoniwj@torproject.org2023-08-23T13:24:18Zurn:sha1:27bdc971415837c18bbfe8911266e251d853b754
clippy: Suppress needless_pass_by_value in tests
See merge request tpo/core/arti!1535Run maint/add_warning to add lint block everywhere2023-08-23T09:34:00ZIan Jacksonijackson@chiark.greenend.org.uk2023-08-22T14:28:12Zurn:sha1:42df88d6bf6dbb460d2e5e1cd4838aafaffbe9actor-rtmock: Relax Sync bound on spawned tasks in MockExecutor2023-08-23T08:59:37ZIan Jacksonijackson@chiark.greenend.org.uk2023-08-18T16:54:45Zurn:sha1:919c955f0f51c66ccc01639c2d8717acf8dfe924
Sync is actually otiose - and I'm about to have some test cases with
futures that aren't Sync.
tor-rtmock: Expose time_until_next_timeout on MockRuntime2023-08-23T08:59:37ZIan Jacksonijackson@chiark.greenend.org.uk2023-08-18T16:43:22Zurn:sha1:6918a7869edbc080dac229cb6f701db93fc9c960Run add_warnings on all files.2023-08-04T11:45:04ZNick Mathewsonnickm@torproject.org2023-08-04T11:45:04Zurn:sha1:cec6d0ce33b4b5cebbce57f55faec83397e9c953Remove semver.md files now that 1.1.7 is out.2023-08-01T16:55:52ZNick Mathewsonnickm@torproject.org2023-08-01T16:55:52Zurn:sha1:1e96d1b95a81a291e040ddeb15e6308c1f1094bdIncrement 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
```
Update minor versions on crates that have had breaking changes2023-08-01T14:51:25ZNick Mathewsonnickm@torproject.org2023-08-01T14:51:25Zurn:sha1:6f2ae5960393b64c1d7615d2d523e050d3bebe5a
These crates had first-order breaking changes:
```
retry-error
tor-keymgr
tor-proto
tor-hsclient
tor-rtmock
```
Additionally, these broke because they re-exposed RetryError:
```
tor-circmgr
```
Additionally, these broke because they may re-expose something from
tor-proto:
```
arti-client
tor-chanmgr
tor-dirclient
tor-dirmgr
tor-guardmgr
```
Additionally, these broke for other fiddly reasons:
`tor-ptmgr` implements traits from tor-chanmgr, which has a breaking
change above.
`arti-hyper` exposes types from arti-client in its API.
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.)