mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.9 2023-09-05T16:22:19Z 2023-09-05T16:22:19Z Nick Mathewson nickm@torproject.org 2023-09-05T16:22:19Z urn:sha1:e251baa9a77415f3c605ff462a8ac0b3fa37660a These are: ``` hashx equix tor-async-utils tor-error tor-config tor-rtmock tor-llcrypto tor-bytes tor-hscrypto tor-hspow tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-netdir tor-chanmgr tor-guardmgr tor-dirmgr tor-keymgr tor-hsclient tor-hsservice arti-client arti ``` 2023-08-15T15:34:31Z Gabriela Moldovan gabi@torproject.org 2023-08-15T15:34:31Z urn:sha1:31645f4f373e821482b95ee4b9e1bd5856ed76aa Previously we were using backtrace 0.3.39, which has a [bug] that causes it to segault in some circumstances. I experienced this bug while trying to fix the minimal-versions build in !1508. [bug]: https://github.com/rust-lang/backtrace-rs/issues/267 2023-08-01T15:40:26Z Nick Mathewson nickm@torproject.org 2023-08-01T15:40:26Z urn:sha1:3422169ff4158e56764e2f3c3d2fea31e8031fcd Vesion bumps for 1.1.7. See merge request tpo/core/arti!1458 2023-08-01T14:57:55Z Nick Mathewson nickm@torproject.org 2023-08-01T14:57:55Z urn: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 ``` 2023-08-01T14:51:25Z Nick Mathewson nickm@torproject.org 2023-08-01T14:51:25Z urn: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. 2023-08-01T12:32:20Z Nick Mathewson nickm@torproject.org 2023-08-01T12:32:20Z urn:sha1:9ce6f0a0eb32051ef36bed2c65f0794a5a04421d 2023-07-19T13:16:13Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-18T10:09:54Z urn:sha1:882ce8c8ce74d393b6d95dcede6e69a1a2e86c9b This code came from tor-error. So now tor-error depends on retry-error. 2023-07-07T17:38:24Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-07T16:43:26Z urn: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. 2023-07-07T13:00:31Z Nick Mathewson nickm@torproject.org 2023-07-07T12:47:49Z urn:sha1:023d288ba228b494500eb9c8ee91c6bde5f62a93 (Also, document that this static assertion is the reason why you are seeing a confusing error message.) 2023-07-07T13:00:31Z Nick Mathewson nickm@torproject.org 2023-07-06T17:48:01Z urn:sha1:7168feefdd41b110646428a087d0b76da990239e The main contribution here is a set of convenience macros for logging error `Report`s. Notably, this macros always logs `Internal` and `BadAspiUsage` errors at `WARN`, unless they are already at `ERROR` or more. This is a little tricky because `tracing::event!()` requires its Level argument to be a constant.