mirrors/arti.git/crates/tor-circmgr, 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.
tor-circmgr: impl AsRef<dyn std::error::Error> for some error types2023-07-18T12:10:03ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-18T11:12:01Zurn:sha1:dd5ceed79144f1750cd63fcfee27885e70b1b015
We're about to want this.
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!1396rng ranges: Use gen_range_infallible() for Duration::ZERO..=T2023-07-10T15:08:03ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T13:19:55Zurn:sha1:b151237a7f8651ed8694748832af05786a7eccfdrng ranges: Use gen_range_checked().unwrap() in test case2023-07-10T15:07:18ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T13:18:32Zurn:sha1:8ae759ef9578d065a9021a2670bbb78c5bfe46b7
Ideally we would be allowed to use vanilla gen_range() here, but there
doesn't seem to be a way to allow a specific clippy-forbidden method
using #[allow] and we probably don't want to make a blanket allow.
rng ranges: Use gen_range_checked().expect() in obvious cases (fmt)2023-07-10T15:07:18ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T15:17:32Zurn:sha1:332285015f7d8c4a4e4edd260425bb06f7399e75rng ranges: Use gen_range_checked().expect() in obvious cases2023-07-10T15:07:18ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T12:47:04Zurn:sha1:5e10805ede1cc1452d37fa3fb8841127f3060a88
In each of these, it is locally obvious that the range is nonempty.
Run maint/add_warning to actually apply new lint allows2023-07-10T12:49:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-10T11:19:32Zurn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0Merge branch 'inclusive' into 'main'2023-07-07T17:07:58ZNick Mathewsonnickm@torproject.org2023-07-07T17:07:58Zurn:sha1:7d1c8dfde0f2b9c545fdff78885856fdc8a101f0
rng ranges: Use inclusive Duration ranges in several places
See merge request tpo/core/arti!1385