mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.12 2024-01-09T13:17:45Z 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 2023-12-14T00:51:39Z Jim Newsome jnewsome@torproject.org 2023-12-14T00:51:39Z urn:sha1:cc9d656ca88d75970cc527af1299e9a1e292b008 Without this change, if the delay is less than one second, the code will effectively busy-loop until the delay has elapsed. This potentially leads to deadlock in shadow simulations, and wastes CPU in real usage. https://shadow.github.io/docs/guide/limitations.html?highlight=busy#busy-loops 2023-12-14T00:50:32Z Jim Newsome jnewsome@torproject.org 2023-12-14T00:50:32Z urn:sha1:10aff4d04e1a404f7f04fde93980184d5b613fb2 2023-12-04T16:35:23Z Nick Mathewson nickm@torproject.org 2023-12-04T16:22:58Z urn:sha1:fba95e4b4708929ed09554632acd2e9f15e3c086 This crate is new, and gets a bump to 0.1.0. tor-log-ratelim This crate had a breaking change: tor-persist tor-llcrypto had a breaking change. These crates _are_ tor-llcrypto, or (transitively) depend on it. I am assuming that they all re-expose something from it in a way that matters: tor-llcrypto tor-bytes tor-hscrypto tor-socksproto tor-checkable tor-cert tor-linkspec tor-cell tor-proto tor-netdoc tor-consdiff tor-netdir 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-hyper 2023-12-04T16:33:36Z Nick Mathewson nickm@torproject.org 2023-12-04T16:22:58Z urn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890 These crates had backward-compatible changes, and get a patchlevel bump only: fs-mistrust tor-error tor-config tor-rtcompat tor-rtmock This crate exposes no non-CLI APIs, and gets a patchlevel bump only: arti 2023-11-28T16:35:51Z Nick Mathewson nickm@torproject.org 2023-11-28T16:35:51Z urn:sha1:1b53c4ca3059fc395c98e2e6d0eb3b58f37c8ec1