mirrors/arti.git/crates/tor-cell/tests/testvec_chanmsg.rs, branch ios-sqlite-hacks mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=ios-sqlite-hacks 2023-02-09T15:20:31Z Change tor_bytes::Error::BadMessage to a Cow. 2023-02-09T15:20:31Z Nick Mathewson nickm@torproject.org 2023-02-08T13:51:27Z urn:sha1:48ab7b0463aaada172a426ad4b20a63d7f44cb84 Actually, to avoid making a breaking change, I'm deprecating BadMessage and creating a new InvalidMessage variant that takes a Cow. This way I don't need to track every crate that re-exposes tor_bytes::Error and call this a breaking change in those. Making this change will allow tor_bytes errors to be much more helpful. tor-cell: Rename ChanMsg and ChanCell-related types. 2023-02-07T21:03:14Z Nick Mathewson nickm@torproject.org 2023-02-07T14:12:02Z urn:sha1:d99c13067939bd256614796be0a50637c3a2b3eb tor-cell: Remove ChanMsg methods that are duplicated in ChanMsgClass. 2023-02-07T21:03:14Z Nick Mathewson nickm@torproject.org 2023-02-07T13:48:34Z urn:sha1:3c7aea723bc49dac09eeb4bcc1acb40f6094e2d5 tor-cell: Use macro to generate ChanMsg too. 2023-02-07T21:03:14Z Nick Mathewson nickm@torproject.org 2023-02-06T19:51:29Z urn:sha1:71445f7ace187d824e535949dfbe781c7db03197 Disable clippy::unlinlined-format-args 2023-01-27T13:27:47Z Nick Mathewson nickm@torproject.org 2023-01-27T12:49:39Z urn:sha1:bf04641c6818cb2c87c6ed9cf463a5710f8919d2 This warning kind of snuck up on us! (See #748) For now, let's disable it. (I've cleaned it up in a couple of examples, since those are meant to be more idiomatic and user-facing.) Closes #748. msg::{CreateFast/CreatedFast}: Rename accessor to (into_)body() 2022-12-19T05:00:24Z Neel Chauhan neel@neelc.org 2022-12-19T05:00:24Z urn:sha1:b649a1d86fe6b42a7021769b24f76ef5e15bf62c tor-cell: Rename for_client and for_relay 2022-10-21T11:21:52Z Emil Engler me@emilengler.com 2022-10-21T11:20:06Z urn:sha1:e5429a28918840d43b5c7ec25d9440d3ba78d8d3 This commit renames the for_client and for_relay functions to from_client and from_relay respectively, in order to indicate their origin, as the term "for" is more likely to indicate a destination, which is not true in that situation. tor-cell: PaddingNegotiate::start: take IntegerMilliseconds 2022-08-17T09:54:41Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-08-08T14:58:32Z urn:sha1:14c6e17797e0ac09b5ec528465567e4ba5ac11ca chancell: PaddingNegotiate: Provide two constructors, not one 2022-08-16T17:37:06Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-07-08T11:15:41Z urn:sha1:0df72449b8596ce22ceb5798c294c676bc45e8f2 We don't really want the caller to pass ignored timeout parameters. And this makes more semantic sense. The stop constructor uses zero, which is what C Tor does. See https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/76 tor-cell: Make encoding method signatures fallible. 2022-07-11T15:18:51Z Nick Mathewson nickm@torproject.org 2022-07-09T17:15:13Z urn:sha1:a0a88643f8a6972d2664ea4268d21d596d0e3c56