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-04T19:41:15Z Nick Mathewson nickm@torproject.org 2025-02-04T17:28:02Z urn:sha1:dffe9330ab57d90f844f2aac950e4cbc2fc7a70b We want to explain better what has happened, not only with the final fatal error, but with any nonfatal errors that occurred in the middle. Closes #1826. 2025-02-04T19:41:15Z Nick Mathewson nickm@torproject.org 2025-02-04T15:40:03Z urn:sha1:921ae4c6cea7893aae854e562720310388b8897b Closes #1650. 2025-02-04T19:41:15Z Nick Mathewson nickm@torproject.org 2025-02-04T15:20:43Z urn:sha1:c8f614faf5084c300a71b6e607a0b189df8830da In general, we try to obey the convention that an error's Display method does not display that error's sources. Part of #1650. 2025-02-03T18:41:15Z Nick Mathewson nickm@torproject.org 2025-02-03T18:41:15Z urn:sha1:7686f3a460ae511410f9e51f54e457635a972289 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-02-03T16:57:39Z Nick Mathewson nickm@torproject.org 2025-02-03T16:57:39Z urn:sha1:150dbc30a6c9d85a51847ad77193040fae3e0506 This was the slowest test in our suite. 2025-01-30T18:28:11Z Nick Mathewson nickm@torproject.org 2025-01-30T18:28:11Z urn:sha1:f8d9cedfeecdb9bcdc7b006845c9856fed302f1f rpc: Document what is actually going on with stream optimism. Closes #1583 See merge request tpo/core/arti!2753