mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.0 2024-03-04T14:51:56Z 2024-03-04T14:51:56Z Gabriela Moldovan gabi@torproject.org 2024-02-29T19:04:58Z urn:sha1:9ca957705291301d90680fce8d537a085cc1ce67 APIs were broken in these pre-1.0.0 crates: ``` tor-keymgr tor-config tor-checkable tor-circmgr tor-dirmgr tor-hsclient tor-hsservice tor-hsrproxy ``` Done with: ``` cargo set-version --bump minor -p tor-keymgr cargo set-version --bump minor -p tor-config cargo set-version --bump minor -p tor-checkable cargo set-version --bump minor -p tor-circmgr cargo set-version --bump minor -p tor-dirmgr cargo set-version --bump minor -p tor-hsclient cargo set-version --bump minor -p tor-hsservice cargo set-version --bump minor -p tor-hsrproxy ``` 2024-03-04T14:51:49Z Gabriela Moldovan gabi@torproject.org 2024-02-29T19:01:41Z urn:sha1:1beb705eefe18bccbc6f29ab522d33a611c78c7b APIs were added: ``` tor-units tor-cell tor-proto tor-netdir arti-client ``` Done with: ``` cargo set-version --bump patch -p tor-units cargo set-version --bump patch -p tor-cell cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p arti-client ``` 2024-03-04T12:24:40Z Gabriela Moldovan gabi@torproject.org 2024-02-29T18:44:43Z urn:sha1:6dc49da2126c5da00790de3892ff1ea49c542dc7 This includes: ``` fs-mistrust tor-linkspec tor-chanmgr ``` Done with ``` ./maint/bump_nodep fs-mistrust tor-linkspec tor-chanmgr ``` 2024-02-12T11:38:36Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-02-12T11:07:42Z urn:sha1:c35c60f848154e80f23ba95a989ff2f9d2594e6a Since Rust 1.66, std's default works properly for enums, provided that the default variant is a unit. Review all uses of `#[educe(default)]` on enums and replace them with std where possible, which is most of them. In 1.66 and later, std's `#[derive(Default)]` doesn't infer any generic bounds on the derived impl, where it's an enum - since the unit variant can always be constructed. So this change doesn't add any generic bounds and is not API-visible. 2024-02-05T16:13:29Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-02-05T16:13:29Z urn:sha1:af615d87e20d0984f493dfb8dda7b0654d8d7304 Bump the minor version of these crates, and update the in-tree dependencies. Recently published as fresh crates, let's just assume there are breaking changes: fslock-guard test-temp-dir Breaking API change affecting many many downstream crates: tor-rtcompat Downstream crates which we're (conservatively) assuming have tor-rtcompat types in their APIs: tor-rtmock tor-log-ratelim tor-rpcbase tor-llcrypto tor-protover tor-bytes tor-hscrypto tor-hspow tor-socksproto tor-checkable tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-consdiff tor-netdir tor-congestion tor-persist tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr tor-keymgr tor-hsclient tor-hsservice tor-hsrproxy arti-client arti-rpcserver arti-config arti-hyper arti-bench arti-testing 2024-01-09T13:17:45Z Nick Mathewson nickm@torproject.org 2024-01-09T13:17:45Z urn:sha1:8e883e2b00d717985746c2402bc6ee394cfd3fdf These crates had no changes previously, but they depend on crates that had breaking changes themselves. tor-linkspec tor-hspow 2024-01-09T13:11:17Z Nick Mathewson nickm@torproject.org 2024-01-09T13:07:43Z urn:sha1:ef150707800e7aba78948f0b5dc5a2dcefaf62b6 This crate doesn't have a meaningful public API, so it just gets a patchlevel bump: arti These crates had nonbreaking changes, and get a patchlevel bump: tor-rtcompat fs-mistrust tor-llcrypto tor-cert 2024-01-09T13:07:43Z Nick Mathewson nickm@torproject.org 2024-01-09T13:07:43Z urn:sha1:565b44dc8e0a40d82b2eb32869b04b807b19cd9c These crates have breaking changes on their own: tor-error tor-netdoc tor-dirmgr tor-keymgr Because of the breaking change in tor-error, and the fact that basically every crate publicly depends on tor-error (by implementing ErrorKind), we need to call this a breaking change on all of the following: tor-config tor-geoip tor-rtmock tor-log-ratelim tor-rpcbase tor-bytes tor-hscrypto tor-socksproto tor-cell tor-proto tor-netdoc tor-netdir tor-persist tor-chanmgr tor-ptmgr tor-guardmgr tor-circmgr tor-dirclient tor-dirmgr tor-keymgr tor-hsclient tor-hsservice tor-hsrproxy arti-client arti-rpcserver arti-config arti-hyper arti-testing 2023-12-14T01:12:10Z Jim Newsome jnewsome@torproject.org 2023-12-14T01:00:37Z urn:sha1:197c5c8b804ed81c6081472ffea84c95a7f621a7 This fixes a race condition that would normally be fairly benign - it would result in scheduling to check for expired channels again immediately, and assuming non-zero time passes would then remove the channel. In Shadow's default time model though, zero time passes in this case, so we just keep scheduling to check again immediately forever; i.e. deadlock. 2023-12-14T01:12:10Z Jim Newsome jnewsome@torproject.org 2023-12-14T00:56:42Z urn:sha1:cc2cbad83958373a5ada310f3d3cab0a49de656d