mirrors/arti.git/crates/arti/src/logging.rs, branch arti-v1.0.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.0.0 2022-08-30T21:48:50Z Mark a few APIs as experimental in docs. 2022-08-30T21:48:50Z Nick Mathewson nickm@torproject.org 2022-08-30T21:48:50Z urn:sha1:a07c4124b1d370b64f3e955a37a532023fc294ad For example, see https://tpo.pages.torproject.net/core/doc/rust/arti/fn.run.html : this isn't labeled as `experimental-api`, but it should be. These APIs were found by poking around in the `arti` crate. arti: Raise the default console log severity to "info" 2022-08-25T13:10:42Z Nick Mathewson nickm@torproject.org 2022-08-25T13:10:42Z urn:sha1:8fa1568b02a3cd4101f65b0e224151cb9813d0bc Previously we logged at "debug", but that's not meant to user-facing. arti: Move most public APIs behind `experimental-api`. 2022-08-11T19:35:32Z Nick Mathewson nickm@torproject.org 2022-08-08T14:14:30Z urn:sha1:f548a6ac55b5f1feb92ea4ffe5c4882a2e19a739 The remaining unconditionally public APIs are those related to our configuration objects, and the main_main() API. The rationale for making main_main() public is to have an actual entry point. The rationale for making the config APIs public is: 1. We really do intend for others to be able to read our configuration files using this API. 2. The structure of our configuration files is already part of our interface. Closes #530. impl_standard_builder: Use for arti::logging::LogfileConfig 2022-06-16T14:42:06Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-06-16T14:13:31Z urn:sha1:c466f13ce35a1f64e17774dbbde195600f09ba83 arti: logging config: Replace a manual Debug impl 2022-06-16T14:27:00Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-06-16T13:53:03Z urn:sha1:c5bbaf470ac992d2af29b3ad60358575b3a34c27 config: Do not strip_option for journald (and in future) 2022-06-10T13:23:13Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-06-10T13:22:05Z urn:sha1:77f33176c31c770aea5e1cdb97d0dbe57f89e674 As per point 1 in https://gitlab.torproject.org/tpo/core/arti/-/issues/488 config: Provide tor_config::resolve_option and resolve journald 2022-05-30T15:00:45Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-27T11:44:04Z urn:sha1:fbfaecdf72be9db7998cf5351351fa8112cef1f4 Canonicalise the `logging.journald` setting in the validated configuration. Now it will never be `Some("")`, even if that is what was written in the config file. This allows us to write `journald = ""` in the example configuration. (Without the canonicalisation the default builder produces `None` and the example would produce `Some("")`, which are semantically identical but fail the test.) See https://gitlab.torproject.org/tpo/core/arti/-/issues/488 for some background. Apply fs-mistrust to logfile directories. 2022-05-24T14:54:02Z Nick Mathewson nickm@torproject.org 2022-05-23T15:43:28Z urn:sha1:25c64db575cc5f8426c026b29cb82ff7fa270c43 impl_standard_builder: Have it generate FooConfig::builder 2022-05-12T17:50:26Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-12T17:15:39Z urn:sha1:be5bc04c02d5023c46a117a048bf0a659094f4eb This deletes many handcoded impls. It also generates lots of impls that we previously didn't have. Rename impl_standard_builder from impl_default_via_builder 2022-05-12T14:59:13Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-05-12T14:58:58Z urn:sha1:c1c6f2b376827c4ebb13bc08456f8355717d15e5 I have Plans for this macro. In particular: * I have a wip branch which tests that the Builder can be deserialised from an empty config (ie, that config reading of a config with a blank section for this item works). * I think we should autogenerate $Config::builder(), and promote that, rather than $ConfigBuilder::default(). This macro could do that.