mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.4 2023-05-03T12:31:11Z 2023-05-03T12:31:11Z Nick Mathewson nickm@torproject.org 2023-05-03T12:31:11Z urn:sha1:1904cfc8b9ca5dd0974dc39516a58a57226f123f Because of the errorkind bumps, we're calling this a breaking change in everything lower-level than `arti`. Generated with: ``` cargo set-version -p tor-basic-utils --bump minor cargo set-version -p tor-async-utils --bump minor cargo set-version -p caret --bump minor cargo set-version -p fs-mistrust --bump minor cargo set-version -p safelog --bump minor cargo set-version -p retry-error --bump minor cargo set-version -p tor-error --bump minor cargo set-version -p tor-config --bump minor cargo set-version -p tor-events --bump minor cargo set-version -p tor-units --bump minor cargo set-version -p tor-rtcompat --bump minor cargo set-version -p tor-rtmock --bump minor cargo set-version -p tor-rpcbase --bump minor cargo set-version -p tor-llcrypto --bump minor cargo set-version -p tor-protover --bump minor cargo set-version -p tor-bytes --bump minor cargo set-version -p tor-hscrypto --bump minor cargo set-version -p tor-socksproto --bump minor cargo set-version -p tor-checkable --bump minor cargo set-version -p tor-cert --bump minor cargo set-version -p tor-linkspec --bump minor cargo set-version -p tor-cell --bump minor cargo set-version -p tor-proto --bump minor cargo set-version -p tor-netdoc --bump minor cargo set-version -p tor-consdiff --bump minor cargo set-version -p tor-netdir --bump minor cargo set-version -p tor-congestion --bump minor cargo set-version -p tor-persist --bump minor cargo set-version -p tor-chanmgr --bump minor cargo set-version -p tor-ptmgr --bump minor cargo set-version -p tor-guardmgr --bump minor cargo set-version -p tor-circmgr --bump minor cargo set-version -p tor-dirclient --bump minor cargo set-version -p tor-dirmgr --bump minor cargo set-version -p tor-hsclient --bump minor cargo set-version -p tor-hsservice --bump minor cargo set-version -p arti-client --bump minor cargo set-version -p arti-rpcserver --bump minor cargo set-version -p arti-config --bump minor cargo set-version -p arti-hyper --bump minor cargo set-version -p arti --bump patch cargo set-version -p arti-bench --bump patch cargo set-version -p arti-testing --bump patch ``` 2023-04-19T16:38:26Z Nick Mathewson nickm@torproject.org 2023-04-19T16:35:49Z urn:sha1:7c1f45a514c0c6f5579be939151a3f75db62d731 2023-04-19T16:38:26Z Nick Mathewson nickm@torproject.org 2023-04-18T22:43:16Z urn:sha1:accd3d858f9812eba326306014a9543590d93dad Right now, this lets us say whether the method was unrecognized or whether the parameter type was incorrect. We'll use this to enforce correct method names later on. (I have to add another `inventory` here, since the `typetag` maintainer does not want to expose this functionality: see https://github.com/dtolnay/typetag/issues/57#issuecomment-1506106290 ) 2023-04-19T16:38:26Z Nick Mathewson nickm@torproject.org 2023-04-18T19:55:08Z urn:sha1:f33aefd76c42165302ab0093d207b8e57ca0192f 2023-04-19T16:38:26Z Nick Mathewson nickm@torproject.org 2023-04-18T17:53:01Z urn:sha1:0503f7bd4bd420df0b06cf9ccdd0b800646108bd This lets us do much less in our rpc_invoke_fn functions. 2023-04-19T16:38:26Z Nick Mathewson nickm@torproject.org 2023-04-18T17:04:28Z urn:sha1:7dcfb02c2201c29cb3237f5921a4130e6fcd567a Now `Method` has an Output and Update associated type, and `decl_method` can do a little more. 2023-04-18T16:00:05Z Ian Jackson iwj@torproject.org 2023-04-18T16:00:05Z urn:sha1:219153a541a4a6d237f54114d604ca70896047fe A few RPC refactorings Closes #817 and #824 See merge request tpo/core/arti!1144 2023-04-16T12:46:42Z Nick Mathewson nickm@torproject.org 2023-04-14T16:35:01Z urn:sha1:5a2c38a1347d0508c59b81ec34732c1ed8fefddd Previously we have two places where we had to do "make a `Drain` sink if updates aren't wanted"; now there's only one. 2023-04-16T12:46:42Z Nick Mathewson nickm@torproject.org 2023-04-14T14:05:56Z urn:sha1:83f5dc48884b66be4c1213f02e403807325cd770 Previously the main loop received updates via a `mpsc::channel`, and final responses via a `futures::unordered`. This could lead to final responses being transmitted to the user before the updates were all flushed. Now all of the responses are sent to the main loop via the same channel, and they can't get out-of-sequence. Closes #817 and (IMO) simplifies the code a bit. 2023-04-16T12:46:41Z Nick Mathewson nickm@torproject.org 2023-04-13T18:14:17Z urn:sha1:3b9fc607637e80bc16876355fbdfa674ce8907f7 Now the update sink is its own boxed object. It is not yet passed to the invoke functions that want it.