mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.0 2025-02-07T10:47:05Z 2025-02-07T10:47:05Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-06T18:24:38Z urn:sha1:d69fe98f10d469028e1cbbd3dff4eabd3ba3d816 Fixes #1841. 2025-02-06T18:17:34Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-06T18:13:25Z urn:sha1:e590ba4d522b44ffc7adc0eea463309df2de12f3 See Release.md. maint/list_crates | grep -P '^tor-|^arti-' | xargs -n1 nailing-cargo -Eu set-version --bump minor -p This completes the version bumps. The report of changed crates, before I started the release work, is: $ maint/changed_crates -v "arti-v$LAST_VERSION" oneshot-fused-workaround: No change. slotmap-careful: No change. test-temp-dir: No change. fslock-guard: No change. hashx: No change. equix: No change. tor-basic-utils: No change. caret: No change. fs-mistrust safelog: No change. retry-error: No change. tor-error tor-general-addr: No change. tor-geoip: No change. tor-rtcompat tor-rtmock tor-async-utils tor-config tor-config-path tor-rpc-connect tor-log-ratelim: No change. tor-rpcbase tor-memquota: No change. tor-units tor-llcrypto: No change. tor-protover: No change. tor-bytes tor-checkable: No change. tor-cert tor-key-forge tor-hscrypto: No change. tor-socksproto: No change. tor-linkspec: No change. tor-cell: No change. tor-proto tor-netdoc: No change. tor-consdiff: No change. tor-netdir tor-relay-selection: No change. tor-persist tor-chanmgr tor-ptmgr: No change. tor-guardmgr: No change. tor-circmgr tor-dirclient: No change. tor-dirmgr: No change. tor-keymgr tor-hsclient tor-hsservice tor-hsrproxy: No change. tor-relay-crypto arti-client arti-relay arti-rpcserver arti arti-rpc-client-core $ 2025-02-06T18:17:34Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-06T18:07:00Z urn:sha1:760400b3de12c5de121b6a7027a29ec78297c863 There are new features. cargo set-version --offline --bump minor -p fs-mistrust Actually, I have discovered by diffing that some methods now take `&self` where previously they took `self`. This will need a further bump to the fs-mistrust version and a fix to the changelog. I will do that. Filed blocker ticket #1841 for it. 2025-02-03T17:00:20Z Nick Mathewson nickm@torproject.org 2025-02-03T17:00:20Z urn:sha1:624b3b4bcb833954a34bdae4c8f1215ac9a44652 Fixes #1831. I'm doing this because switching from the socketpair crate to an ersatz connect-to-localhost socketpair made the test pass. My windows skills are weak, but it appears possible that you aren't supposed to simultaneously have a blocking ReadFile and a blocking WriteFile to a named pipe from separate threads? At least, that's consistent with our findings in !2758. I first saw this hack in perl, when I needed it in 2003. I am displeased that it is still apparently needed in 2025. 2025-01-15T14:18:44Z Nick Mathewson nickm@torproject.org 2025-01-09T19:08:20Z urn:sha1:08e9de49b3a0f9d428b4e28e1eefceaba9fe74a8 2025-01-15T14:18:44Z Nick Mathewson nickm@torproject.org 2025-01-09T18:56:46Z urn:sha1:94b598931b540f8cf96e70a1d8bf79a72034fc8e 2025-01-07T16:01:41Z Nick Mathewson nickm@torproject.org 2025-01-07T14:46:55Z urn:sha1:8f4297f5e2712213910b50ced205c7b5aa0619b5 The affected crates follow our regular versioning. They all get bumped to 0.26.0. Done with ``` for crate in $(./maint/list_crates |grep '^arti-\|tor-' ); do cargo set-version --bump minor -p $crate; done ``` 2025-01-06T13:05:00Z Nick Mathewson nickm@torproject.org 2025-01-06T13:02:37Z urn:sha1:8810732cf7cf79c4746e8eac006d326f21d26c5f 2024-12-09T20:23:43Z Nick Mathewson nickm@torproject.org 2024-11-25T20:22:19Z urn:sha1:dd9e01c8499eaa5db6179cd4bb7a6020e9c2b9c5 This commit covers the major points of the design: Parsing the environment, parsing and resolving connect points, connecting to Arti, and handling errors. There are a few areas that need to be fixed, all marked with XXXXs. 2024-12-09T20:23:43Z Nick Mathewson nickm@torproject.org 2024-11-25T14:12:12Z urn:sha1:f55196bd8736203dad61dcf4228942308b005975