mirrors/arti.git/crates/tor-error, 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!1458Increment 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:9ce6f0a0eb32051ef36bed2c65f0794a5a04421dretry-error: Provide fmt_error_with_sources in retry-error2023-07-19T13:16:13ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-18T10:09:54Zurn:sha1:882ce8c8ce74d393b6d95dcede6e69a1a2e86c9b
This code came from tor-error. So now tor-error depends on
retry-error.
clippy: tor-error: Use convert::identity for into_internal!2023-07-10T12:49:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-10T12:38:24Zurn:sha1:fd2e4979be7007f79a0c2c47ac8b89db8ee534cb
This launders the closure so that clippy's
clippy::redundant_closure_call can't see it.
We can't have a local #[allow] because it would be on an expression,
which isn't allowed on stable.
This avoids having to use more clumsy idioms at call sites.
Run maint/add_warning to actually apply new lint allows2023-07-10T12:49:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-10T11:19:32Zurn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0Fix warn_report and error_report macros.2023-07-07T19:46:41ZNick Mathewsonnickm@torproject.org2023-07-07T19:46:41Zurn:sha1:53c599d50f6394a301f0aa491454bd69ba42a962
Originally they didn't check err.kind(), since err.kind() can never
increase their severity. We lost that behavior with !1386, and we
became dependent on it with arti!1383. Since they both merged at
the same time, CI broke.
This patch restores their original behavior.
tor-error: tracing module: Use macro to generate macros2023-07-07T17:38:24ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T16:43:26Zurn:sha1:696adc3c9407019a7969eeff9680d8ed668a730b
This abolishes some quintuplication.
The output is identical except that:
* The syntax display in the rustdoc output for the resulting macros
seems to have somewhat less whitepsace.
* The whimsical error messages in the examples are all identical.
Ah well.
tor-error: tracing module: Fix link to tracing macro2023-07-07T16:48:05ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-07T16:47:50Zurn:sha1:220900a852308042c237317eaca411782f0d0bd6