mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0 2022-05-27T14:18:52Z 2022-05-27T14:18:52Z Nick Mathewson nickm@torproject.org 2022-05-27T14:18:52Z urn:sha1:4326aa1de9875ea399c3a608c0320bbe4b214a42 This commit was made by reverting the previous commit, then re-running the script I used to generate it. In theory there should be no semantic changes: only changes due to improved formatting from cargo edit. 2022-05-27T13:01:20Z Nick Mathewson nickm@torproject.org 2022-05-27T13:01:20Z urn:sha1:b232365a75249d6f767127feb2a47286f9ece762 I followed the following procedure to make these changes: * I used maint/changed_crates to find out which crates had changed since 0.3.0. * I used grep and maint/list_crates to sort those crates in topological (dependency) order. * I looked through semver_status to find which crates were listed as having semver-relevant changes (new APIs and breaking changes). * I scanned through the git logs of the crates with no semver-relevant changes listed to confirm that, indeed, they had no changes. For those crates, I incremented their patch-level version _without_ changing the version that other crates depend on. * I scanned through the git logs of the crates with no semver-relevant changes listed to confirm that, indeed, they had no obvious breaking changes. * I treated all crates that depend on `arti` and/or `arti-client` as having breaking changes. * I identified crates that depend on crates that have changed, even if they have not changed themselves, and identified them as having a non-breaking change. * For all of the crates, I used `cargo set-version -p $CRATE --bump $STATUS` (where `STATUS` is `patch` or `minor`) to update the versions, and the depended-upon versions. 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. 2022-05-19T12:09:05Z Nick Mathewson nickm@torproject.org 2022-05-19T12:09:05Z urn:sha1:5b5b4bbbea7217969509dd3a20318744ecf247cd 2022-05-19T12:04:57Z Nick Mathewson nickm@torproject.org 2022-05-19T12:04:57Z urn:sha1:eab0046d0ea87e7d80ff4dadf2e71dc326809521 2022-05-19T12:00:41Z Nick Mathewson nickm@torproject.org 2022-05-19T12:00:41Z urn:sha1:6aebb18e64f148d6f554ad1bd84e19b0128e121a It does nothing that Fatal does not. Suggested by @eta in review. 2022-05-17T18:58:36Z Nick Mathewson nickm@torproject.org 2022-05-17T18:58:36Z urn:sha1:c70916c0d986e71894778e17483d039788d6e553