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-24T19:14:57Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-24T18:07:25Z urn:sha1:9e526aad7c4ca37e8ee9b082449da6493b6e475b This gets rid of `#[serde(flatten)]` which prevents serde_ignored (and other kinds of introspection) from working properly. The price is now that the toplevel has to deal with two configuration objects. The Resolvable trait is overkill right now, but is going to do More Things in a moment. In particular, we need the impl on tuples, so that the whole config can be processed in one go. 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-13T11:42:30Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-13T10:42:51Z urn:sha1:4e2bd6c7983dfa1adab59180e034c68bbe167daf 2022-05-13T11:42:30Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-13T10:36:28Z urn:sha1:ef36882807dbd6e5dabdd2d40fe4543fb29443ee Generally, change the paths that mention the crate name to go via a module-level "use". This involves adding tor-config as a direct dependency for a few crates. 2022-05-13T09:56:56Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-12T15:36:28Z urn:sha1:58c753429f299d10fd60303d10ca085863ce3717 This is a benchmarking tool, and fs-mistrust doesn't like the permissions in our CI. The env var ARTI_FS_DISABLE_PERMISSION_CHECKS is (of course) specific to arti. Maybe it should be honoured here, or this should be done via the config files. But disabling this is fine for now. 2022-05-11T14:53:03Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-11T11:03:07Z urn:sha1:e363b79a01b1aa19e9407755d67057524775cd95 This emphasises its nature. We're going to provide a more cooked constructor in a moment. 2022-05-06T14:03:15Z Nick Mathewson nickm@torproject.org 2022-05-06T14:03:15Z urn:sha1:7b93091f57f43ec8543a17052d60a2c8f7f2b0cc * Except for safelog and fs-mistrust, which are new. 2022-05-05T09:19:29Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-04T16:44:26Z urn:sha1:6a39f9d8da2c3f2b1a91564003c510e143ffe33f Having a consistent order will make the nest commit easier to read.