mirrors/arti.git/crates/tor-guardmgr, 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-guardmgr: bridges: getter for BridgeConfigBuilder.transport2023-07-20T15:42:03ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-20T15:34:32Zurn:sha1:3343e70c6822c38d60adb3658af7bb36d3a04337
BridgeConfigBuilder is Serialize so this isn't making any new API
promises. Ideally we'd have getters like this everywhere.
Merge branch 'bug638' into 'main'2023-07-14T13:35:04ZAlexander Færøyahf@torproject.org2023-07-14T13:35:04Zurn:sha1:63a3bbc33cead7cc292ecee15f036a61ecd3b6f0
Stop unconditionally marking bridges as having dir info.
Closes #638
See merge request tpo/core/arti!1408Bridges: deduplicate addresses.2023-07-13T20:58:12ZNick Mathewsonnickm@torproject.org2023-07-13T20:58:12Zurn:sha1:b8334292fb11494f8a9bf768a8c5b606ef3ce79f
Currently we list an address for a bridge twice if it is listed both
in the bridge line and the bridge descriptor. That can't be right.
Better report for any recurrence of bug #638.2023-07-13T19:43:57ZNick Mathewsonnickm@torproject.org2023-07-13T19:42:24Zurn:sha1:3f2d4f8cec2c349ab38f7e4a006f3396318027ceStop unconditionally marking bridges as having dir info.2023-07-13T19:43:42ZNick Mathewsonnickm@torproject.org2023-07-13T19:28:36Zurn:sha1:7a915f5454599ee0042fe243a82a78510501c76f
When we implemented bridges, we added code in 08473872abccf389 to
conditionally mark their directory info as present or not present.
But the we didn't remove the old code to mark them present
unconditionally!
Fixes #638.
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:b151237a7f8651ed8694748832af05786a7eccfdRun maint/add_warning to actually apply new lint allows2023-07-10T12:49:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-10T11:19:32Zurn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0