mirrors/arti.git/crates/tor-rtmock, 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
```
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.)
Upgrade to latest derive-adhoc.2023-07-17T14:24:38ZNick Mathewsonnickm@torproject.org2023-07-17T14:24:38Zurn:sha1:a783a4f93235b5d0358b58f757afcad8d940ed5fRun maint/add_warning to actually apply new lint allows2023-07-10T12:49:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-10T11:19:32Zurn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0Add exceptions for some cases of diverging_sub_expression2023-07-10T11:33:21ZNick Mathewsonnickm@torproject.org2023-07-07T18:17:52Zurn:sha1:0b6cc7ba5ed6962bb6cf568a8bdc788de4c329f6
See here for documentation on the lint:
https://rust-lang.github.io/rust-clippy/master/index.html#/diverging_sub_expression
The issue here, from what I can tell, is that the lint triggers
whenever you use a diverging expression as a function body within an
Merge branch 'da-task' into 'main'2023-07-10T10:53:23Zgabi-250gabi@torproject.org2023-07-10T10:53:23Zurn:sha1:2db3e7343480228a26204e8b3f9c333c3fc63f22
RFC: tor-rtmock: Use derive-adhoc for composite runtimes
See merge request tpo/core/arti!1381tor-rtmock: Use derive-adhoc for composite runtimes2023-07-07T09:26:44ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-06T14:46:35Zurn:sha1:6e495d8400e9e5b0deb087d572f821d7fd802b8fRun add_warning to remove `missing_panics_doc` deny.2023-07-06T18:32:23ZNick Mathewsonnickm@torproject.org2023-07-06T18:32:23Zurn:sha1:03f9f9987a7ba42368d82363bef7f569e32ffe2c
Closes #950.
tor-rtmock: statically assert that the macro makes a Runtime impl2023-07-06T14:58:42ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-06T14:46:03Zurn:sha1:de97288c5325b331ef0805be16ead1ec73cb3941