mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.1 2024-12-02T15:41:21Z 2024-12-02T15:41:21Z Gabriela Moldovan gabi@torproject.org 2024-12-02T15:39:29Z urn:sha1:e29e7a9aab4312af6a35818cb01676376d888e49 Done using: ``` for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.25.0 done ``` 2024-12-02T15:41:21Z Gabriela Moldovan gabi@torproject.org 2024-12-02T15:32:52Z urn:sha1:158ff2d2c0ef59ce6cdf5e8d6fe499b50e762002 The non-{arti-,tor-} crates are: ``` ./maint/list_crates | rg -v '^(tor|arti)' oneshot-fused-workaround slotmap-careful test-temp-dir fslock-guard hashx equix caret fs-mistrust safelog retry-error ``` We split them in the following categories: * crates with no changes (no version bumps): ``` maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-' oneshot-fused-workaround: No change. test-temp-dir: No change. caret: No change. ``` * crates that only have non-functional changes (bump the patch version): - slotmap-careful - fslock-guard - hashx - equix - fs-mistrust - safelog - retry-error * crates where APIs were broken (bump minor): None The bumps from this commit were created using this script: ``` PATCH=" slotmap-careful fslock-guard hashx equix fs-mistrust safelog retry-error " for crate in $PATCH; do cargo set-version --bump patch -p $crate; done ``` 2024-11-12T17:00:30Z Clara Engler cve@cve.cx 2024-11-12T10:04:54Z urn:sha1:2f00918ad55881fb8fb37ad51eb644c8aaa16a23 2024-10-30T16:57:34Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-10-30T16:57:34Z urn:sha1:ea6d32087c33405b4f596e9fab52677bd42b900a cargo set-version --bump=patch -p slotmap-careful cargo set-version --bump=patch -p safelog 2024-10-30T16:55:19Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-10-30T16:55:19Z urn:sha1:08ff96ea214b3f4841aac10db77815e5e52c35d0 cargo set-version -p tor-async-utils 0.24.0 cargo set-version -p tor-basic-utils 0.24.0 cargo set-version -p tor-bytes 0.24.0 cargo set-version -p tor-cell 0.24.0 cargo set-version -p tor-cert 0.24.0 cargo set-version -p tor-chanmgr 0.24.0 cargo set-version -p tor-checkable 0.24.0 cargo set-version -p tor-circmgr 0.24.0 cargo set-version -p tor-config 0.24.0 cargo set-version -p tor-config-path 0.24.0 cargo set-version -p tor-consdiff 0.24.0 cargo set-version -p tor-dirclient 0.24.0 cargo set-version -p tor-dirmgr 0.24.0 cargo set-version -p tor-error 0.24.0 cargo set-version -p tor-general-addr 0.24.0 cargo set-version -p tor-geoip 0.24.0 cargo set-version -p tor-guardmgr 0.24.0 cargo set-version -p tor-hsclient 0.24.0 cargo set-version -p tor-hscrypto 0.24.0 cargo set-version -p tor-hsrproxy 0.24.0 cargo set-version -p tor-hsservice 0.24.0 cargo set-version -p tor-key-forge 0.24.0 cargo set-version -p tor-keymgr 0.24.0 cargo set-version -p tor-linkspec 0.24.0 cargo set-version -p tor-llcrypto 0.24.0 cargo set-version -p tor-log-ratelim 0.24.0 cargo set-version -p tor-memquota 0.24.0 cargo set-version -p tor-netdir 0.24.0 cargo set-version -p tor-netdoc 0.24.0 cargo set-version -p tor-persist 0.24.0 cargo set-version -p tor-proto 0.24.0 cargo set-version -p tor-protover 0.24.0 cargo set-version -p tor-ptmgr 0.24.0 cargo set-version -p tor-relay-crypto 0.24.0 cargo set-version -p tor-relay-selection 0.24.0 cargo set-version -p tor-rpcbase 0.24.0 cargo set-version -p tor-rtcompat 0.24.0 cargo set-version -p tor-rtmock 0.24.0 cargo set-version -p tor-socksproto 0.24.0 cargo set-version -p tor-units 0.24.0 cargo set-version -p arti-client 0.24.0 cargo set-version -p arti-relay 0.24.0 cargo set-version -p arti-rpc-client-core 0.24.0 cargo set-version -p arti-rpcserver 0.24.0 2024-10-25T18:52:35Z Neel Chauhan neel@neelc.org 2024-10-25T18:52:35Z urn:sha1:133c0ac0c0d87d062bc2febe9bc355e25af11c2b 2024-10-25T18:51:44Z Neel Chauhan neel@neelc.org 2024-10-16T23:07:28Z urn:sha1:12301c4bfa97367af917a5889af08bfef5b7e125 2024-10-24T01:35:05Z Nick Mathewson nickm@torproject.org 2024-10-24T00:48:42Z urn:sha1:270234f81c3a2fc5f56fbe3d71cabad672237a78 2024-10-24T01:35:05Z Nick Mathewson nickm@torproject.org 2024-10-24T00:44:08Z urn:sha1:797a9d21dd856e62a0525130d34d5a992b7f9a7c 2024-10-24T01:35:05Z Nick Mathewson nickm@torproject.org 2024-10-24T00:33:55Z urn:sha1:eb1d9acd10c5d500f56d637a7bba3acdd67dc9e8 This commit removes the separate function for asking whether to bypass the dispatch code. Instead, it gives the "invoke with bypass" function an error to return when no dispatch is warranted, and moves the whole responsibility for method dispatch or non-dispatch back into tor-rpcbase. I had to add an ObjectId argument to `invoke_rpc_method` to make this work, but that's probably a good thing. Additionally, this commit tweaks the derive-deftly macro to prevent you from asking for dispatch bypass on special methods, where it isn't implemented (and doesn't really make sense).