mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.1 2023-01-27T13:28:02Z 2023-01-27T13:28:02Z Nick Mathewson nickm@torproject.org 2023-01-27T13:01:45Z urn:sha1:a6dd92843edf2bd4c58de62a0d562921e4191ada This panics on error, and we're fine with a panic on misbehavior in tests. 2023-01-20T13:06:30Z Nick Mathewson nickm@torproject.org 2023-01-19T19:50:07Z urn:sha1:889206cde4ef29d7d10bda546f8ad518eb09c290 This is in lieu of upgrading to the latest base64 crate, which has a different API from the old one. Since we have to migrate either way, we might as well use base64ct everywhere. I don't think that most of these cases _require_ constant-time base64, but it won't hurt. 2022-12-12T18:00:29Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-12-12T17:57:37Z urn:sha1:baf78361e848269a24a3019d99f87943872e6012 This is the hunks from running the rune in maint/adhoc-add-lint-blocks but which require some subsequent manual fixup: usually, deleting now-superfluous outer allows, but in some cases manually putting back lints that the adhoc script deleted. 2022-07-22T14:04:25Z Nick Mathewson nickm@torproject.org 2022-07-22T14:04:25Z urn:sha1:41104137b12159d734f1171c1705c4e00f5244cd This name is more accurate because we aren't only dealing with clock skew here: we're also trying to tolerate the case where the authorities fail to reach consensus for a while. 2022-06-13T16:22:04Z Nick Mathewson nickm@torproject.org 2022-06-13T16:22:04Z urn:sha1:68ea880b84c9aedfc276921675f94a257bcc2556 This is all crate-internal APIs, fortunately. 2022-06-13T14:49:09Z Nick Mathewson nickm@torproject.org 2022-06-13T14:40:56Z urn:sha1:f581feb0acff2d80aa825e4c187e62a2a2b61db2 This is about to become only a _part_ of what defines a DirStatus: a DirStatus will also include a reset count, and some kind of info about how long we've gone without progress. 2022-05-25T12:58:37Z Nick Mathewson nickm@torproject.org 2022-05-25T12:58:37Z urn:sha1:0caa5bcba5c3be8aca2fb90331a830d1a22f5e22 Now that the relevant functions now report changed/not-changed status via a boolean out-parameter (see !527), there's no reason to have a separate NoChanged error case. Closes #484. 2022-05-24T19:33:42Z eta tor@eta.st 2022-05-24T19:33:42Z urn:sha1:608d0cbcc25c7576173312d33569de7468449ad6 DirMgr: Stop load-from-cache process when there is no change. Closes #482 See merge request tpo/core/arti!527 2022-05-24T14:54:02Z Nick Mathewson nickm@torproject.org 2022-05-18T17:26:01Z urn:sha1:95200383b52d1644d4de357c2a8a50d91fdc1021 This is an approximately minimal revision to get Builder in place; subsequent commits will clean up the API. 2022-05-24T12:50:20Z Nick Mathewson nickm@torproject.org 2022-05-24T12:50:20Z urn:sha1:8e15c97f56f19ff63cb208f1832827860ad56925 Previously in !511 I had introduced a bug where, if there was an error more serious than "no change", that error would keep us from noticing that we had no change, and we'd loop until the safety counter ran out. Then we'd panic. This commit fixes the bug by reintroducing the `changed` boolean -- this time as an outparam for the add_from_* methods. Fixes #482.