mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.1.0 2022-01-21T15:59:14Z 2022-01-21T15:59:14Z Nick Mathewson nickm@torproject.org 2022-01-21T15:51:59Z urn:sha1:c3f82ee14daede464af7ed750e215a01908d5188 Explain how to report bugs and how get accounts on the bugtracker; add link to the troubleshooting document. Part of #277 2022-01-20T17:36:37Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-01-20T17:36:37Z urn:sha1:1250fc68cece55c521dcff49ddc5a5167b50a0b5 Eventually we may need a separate HACKING.md 2021-12-20T18:52:13Z Nick Mathewson nickm@torproject.org 2021-12-20T16:31:20Z urn:sha1:d82d70939e4833df7327d10866e1f8955f97234f 2021-10-27T18:11:48Z eta tor@eta.st 2021-10-27T16:40:00Z urn:sha1:4fa0122dde2b664ebd10bfbe46da54c396dffdb3 This switches out `arti`'s argument-parsing library with `clap`, which is a lot more featureful (and very widely used within the Rust ecosystem). We also now use a lot of `clap`'s features to improve the CLI experience: - The CLI now expects a subcommand (currently, either "help", or "proxy" for the existing SOCKS proxy behaviour). This should let us add additional non-SOCKS-proxy features to arti in future. - `clap` supports default values determined at runtime, so the way the default config file is loaded was changed: now, we determine the OS-specific path for said file before invoking `clap`, so the help command can show it properly. - The behaviour of `tor_config` was also changed; now, one simply specifies a list of configuration files to load, together with whether they're required. - That function also way overused generics; this has been fixed. - Instead of using the ARTI_LOG environment variable to configure logging, one now uses the `-l, --log-level` CLI option. (The intent is for this option to be more discoverable by users.) - The `proxy` subcommand allows the user to override the SOCKS port used on the CLI without editing the config file. 2021-10-25T16:58:42Z Dimitris Apostolou dimitris.apostolou@icloud.com 2021-10-25T16:58:42Z urn:sha1:c26dc07fbbeac2d3e8a81029f2c7bbc2112b738b 2021-09-09T07:38:29Z Jani Monoses jani.monoses@gmail.com 2021-09-09T07:36:08Z urn:sha1:4d52f99020830b463a8b74a86418e9a0d5f66f3f 2021-08-26T14:54:06Z Jani Monoses jani.monoses@gmail.com 2021-08-25T10:27:02Z urn:sha1:df73dfe0c8459ec271131d7e48916ec41151f9c1 Replace the trace config file option with a more flexible trace_filter and expose the same via the ARTI_LOG environment variable. If ARTI_LOG is set it will override the setting in the config file. Example: ARTI_LOG="info,tor_proto::channel=trace" ./target/debug/arti The syntax is described here https://docs.rs/tracing-subscriber/0.2.20/tracing_subscriber/filter/struct.EnvFilter.html#directives 2021-08-24T19:53:43Z Nick Mathewson nickm@torproject.org 2021-08-24T19:53:43Z urn:sha1:729fccba0ce45561c9422ff843ee9d9e1fbb525c 2021-08-24T19:50:51Z Nick Mathewson nickm@torproject.org 2021-08-24T19:50:51Z urn:sha1:e4795c57d0022f70a864097041e48c0f9d5e7bdf 2021-08-09T16:42:10Z Nick Mathewson nickm@torproject.org 2021-08-09T16:42:10Z urn:sha1:abb3e2fad57402e6bb667ece456057f67aca5d81 Mainly, drop the suggestion to fetch submodules, and explain what more things do. (The only submodule we have now is the fuzzing corpora, which most people won't want.) (I am not 100% convinced that we should keep 100% of the instructions for working with git in the long term. Do many other projects have these? Is there a tutorial we should link to instead?)