mirrors/arti.git/crates/tor-hsclient, 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.)
Fix typos2023-07-22T07:10:34ZDimitris Apostoloudimitris.apostolou@icloud.com2023-07-22T07:10:34Zurn:sha1:947ddfff0cfac3fef0e3d7ebc14182c638a1d90btor-hsclient: Document API break.2023-07-19T13:16:13ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-19T13:14:11Zurn:sha1:ad48335b912f9a5bc6a935617e74f8a1ca12abc4
This would be a break in higher-layer crates which incorproate this
error but:
1. That's just arti-client which hides it behind the detailed errors
cargo feature
2. I'm hoping cargo-semver-checks would spot it, anyway.
retry-error: Attempts must be AsRef<dyn Error>; print their sources2023-07-19T13:16:13ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-18T12:07:39Zurn:sha1:36b9d11ecb122e1ea82a13fa963c35e023f14d3a
The effect is that everywhere a RetryError is used, the error sources
for the contained errors will be Display'd.
In tor-hsclient we no longer need to explicitly wrap things up in
tor_error::Report.
Merge branch 'clippy-allow' into 'main'2023-07-11T09:37:42ZIan Jacksoniwj@torproject.org2023-07-11T09:37:42Zurn:sha1:3acc2af4f3411588f80669ae1980679dd260b119
clippy: Allow some of our existing code patterns
See merge request tpo/core/arti!1396Merge branch 'conversation' into 'main'2023-07-10T13:14:11ZAlexander Færøyahf@torproject.org2023-07-10T13:14:11Zurn:sha1:6be6352b987851f2b15d8d8f1a088924ca7b2d9c
Overhaul send_control_message
See merge request tpo/core/arti!1367Merge branch 'recurse' into 'main'2023-07-10T13:13:31ZAlexander Færøyahf@torproject.org2023-07-10T13:13:31Zurn:sha1:943c12739d7a67ca31a2507383a1d9a3c70a65ed
tor-hsclient: Mock traits: Work around an async boobytrap
See merge request tpo/core/arti!1365Run maint/add_warning to actually apply new lint allows2023-07-10T12:49:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-10T11:19:32Zurn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0