mirrors/arti.git/crates/arti-testing, 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-01T15:40:26ZMerge branch 'bump_versions_117' into 'main'2023-08-01T15:40:26ZNick Mathewsonnickm@torproject.org2023-08-01T15:40:26Zurn:sha1:3422169ff4158e56764e2f3c3d2fea31e8031fcd
Vesion bumps for 1.1.7.
See merge request tpo/core/arti!1458Bump patchlevel versions of crates with trivial changes2023-08-01T15:03:56ZNick Mathewsonnickm@torproject.org2023-08-01T15:01:13Zurn:sha1:5cc3fe162944aff8efb975ac966f0e91b6908281
These crates have had trivial changes only: typically,
changes to documentation or to clippy warnings. There's no
good reason to update which version of them other crates depend on,
so we only bump _their_ patchlevels.
```
tor-async-utils
caret
safelog
tor-events
tor-units
tor-rtcompat
tor-rpcbase
tor-llcrypto
tor-protover
tor-bytes
tor-hscrypto
tor-socksproto
tor-cert
tor-cell
tor-consdiff
tor-congestion
arti-rpcserver
arti-testing
arti-bench
arti-config
arti-hyper
```
Increment 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 "fixup features" in preparation for a release.2023-08-01T12:32:20ZNick Mathewsonnickm@torproject.org2023-08-01T12:32:20Zurn:sha1:9ce6f0a0eb32051ef36bed2c65f0794a5a04421dMerge 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:b151237a7f8651ed8694748832af05786a7eccfdRun maint/add_warning to actually apply new lint allows2023-07-10T12:49:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-10T11:19:32Zurn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0rng ranges: Use inclusive Duration ranges in several places2023-07-07T15:13:52ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T13:10:23Zurn:sha1:bcc3e6fef8b863fa6a863aae2d6234fba7fb99f6
Many of these call sites would panic if, somehow, the upper bound was
zero. In most cases it is very complicated to see if whether this
could happen.
However, there is a better answer:
Durations are (conceptually) dense, so picking the closed set (which
includes its boundary) rather than the open one (which doesn't) will
make little practical difference.
So change four call sites to use `..=` instead of just `..`.
Run add_warning to remove `missing_panics_doc` deny.2023-07-06T18:32:23ZNick Mathewsonnickm@torproject.org2023-07-06T18:32:23Zurn:sha1:03f9f9987a7ba42368d82363bef7f569e32ffe2c
Closes #950.