aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | | tor-rtmock: impl Default for MockNetProvider (prep)Ian Jackson2023-07-061-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We want MockNetProvider to be Default. In this commit: impl Default for MockNetwork and use it in new().
| * | | | tor-rtmock: impl Default for MockSleepProviderIan Jackson2023-07-061-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | Pick an arbitrary start time roughly now. This will do for many tests.
| * | | | tor-rtmock: net: "Provide" a UDP "implementation" which doesn't workIan Jackson2023-07-064-5/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Nothing in our tree actually *uses* the UDP in tests. We want a mock UDP provider that isn't part of a real runtime, so that we can make a totally-mock runtime for properly controlled testing. It seems best to make this part of MockNetProvider rather than a separate type.
| * | | | tor-rtmock: Introduce impl_runtime_prelude (fmt)Ian Jackson2023-07-061-1/+3
| | | | |
| * | | | tor-rtmock: Introduce impl_runtime_preludeIan Jackson2023-07-063-17/+26
| | | | | | | | | | | | | | | | | | | | | | | | | This deduplicates some imports, which would otherwise be about to become triplicated.
| * | | | tor-rtmock: Introduce impl_runtime! macroIan Jackson2023-07-064-118/+115
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This deduplicates some trait delegation. We want this now because we're about to introduce a third mock runtime, so this would become triplication otherwise.
* | | | | Merge branch 'log_precision' into 'main'Nick Mathewson2023-07-066-4/+385
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | arti: Add a `logging.time_granularity` option with 1s default. Closes #551 See merge request tpo/core/arti!1376
| * | | | arti: comments about catch_unwindNick Mathewson2023-07-061-0/+9
| | | | |
| * | | | time_granularity: Make sure formatter can't panicNick Mathewson2023-07-061-17/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I was unable to assure myself that tracing_subscriber could withstand a panicking Timer, so instead I'm trying to make sure our own LogTimer can't panic.
| * | | | arti: Add a `logging.time_granularity` option with 1s default.Nick Mathewson2023-07-066-5/+346
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | This lets us provide less information in our logs: in particular, it lets us avoid logging with microsecond precision. Closes #551.
* | | | Merge branch 'tracing-panic' into 'main'Nick Mathewson2023-07-064-2/+42
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | arti: Install a panic hook that sends messages to `tracing` Closes #921 See merge request tpo/core/arti!1377
| * | | | arti: Note possibility for future use of other tracing panic providerNick Mathewson2023-07-061-0/+5
| | | | |
| * | | | arti: On panic, avoid allocation even more.Nick Mathewson2023-07-061-7/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The original version of our panic handler would allocate a string for the panic `Location`. But if we're panicking we'd like to keep allocations to a minimum: so instead format the `Location` conditionally. This also drops a useless `std::borrow::Cow`. (The possibility of a "Don't have a `Cow`" commit message was considered and rejected.)
| * | | | Add TODO comments about possibly migrating away from the backtrace crate.Nick Mathewson2023-07-052-1/+4
| | | | |
| * | | | arti: Install a panic hook that sends messages to `tracing`Nick Mathewson2023-07-053-1/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (Also leaves installed the default handler that sends messages to stderr.) Closes #921.
* | | | | Merge branch 'keymgr-enc-key-todo' into 'main'gabi-2502023-07-051-1/+12
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | keymgr: Explain why the TODO regarding EncodableKey can't be addressed. See merge request tpo/core/arti!1372
| * | | | keymgr: Explain why the TODO regarding EncodableKey can't be addressed.Gabriela Moldovan2023-07-051-1/+12
|/ / / /
* | | | Merge branch 'shadow-onion' into 'main'Nick Mathewson2023-07-0541-29/+133
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | CI: extend shadow test to test an onion service connection See merge request tpo/core/arti!1292
| * | | | CI: enable onion-service-client in rust-latest buildJim Newsome2023-07-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | The shadow test needs this to use this build when testing onion services.
| * | | | articlient-onion: don't filter onion addressesJim Newsome2023-07-033-1/+5
| | | | |
| * | | | Dedupe arti configs and match TestingTorNetworks HS configJim Newsome2023-07-039-49/+17
| | | | |
| * | | | shadow test: disable trace-level loggingJim Newsome2023-07-031-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some hosts were configured to log at trace level instead of the global default (debug level). This was resulting in quite large shadow log output.
| * | | | shadow test: disable worker spinningJim Newsome2023-07-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | This optimization doesn't seem to help much for this test; disable it to avoid burning CI runner CPU.
| * | | | shadow test: enable arti's `log_sensitive_information` optionJim Newsome2023-07-033-0/+9
| | | | |
| * | | | shadow test: fix hidden service dir permissionsJim Newsome2023-07-031-0/+5
| | | | |
| * | | | shadow test: add 2 more relaysJim Newsome2023-07-0321-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | Without this, the onion client was failing to find a guard. We recently made this change in shadow's "tor minimal" test as well.
| * | | | shadow test: fail the test if streams didn't succeedJim Newsome2023-07-031-0/+1
| | | | |
| * | | | shadow test: add and validate arti onion clientJim Newsome2023-07-034-1/+63
| | | | |
| * | | | shadow test: add onion serverJim Newsome2023-07-039-0/+32
| | |/ / | |/| |
* | | | Merge branch 'unpublishing' into 'main'Ian Jackson2023-07-053-0/+10
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | | | | | Mark several crates with `publish=false`. Closes #944 See merge request tpo/core/arti!1371
| * | | Mark arti-bench with "publish = false"Nick Mathewson2023-07-031-0/+4
| | | | | | | | | | | | | | | | | | | | This crate is only useful for development; earlier we published it, but I believe that was in error.
| * | | Mark vestigial crates as "publish=false"Nick Mathewson2023-07-032-0/+6
| |/ / | | | | | | | | | | | | | | | | | | These crates were started, but they aren't integrated into Arti (yet?). As such it doesn't make sense to keep publishing updated versions of them every time we tweak our standard lints.
* | | Merge branch 'faster-ci' into 'main'gabi-2502023-07-042-5/+7
|\ \ \ | | | | | | | | | | | | | | | | try making CI faster See merge request tpo/core/arti!1373
| * | | fix audittrinity-1686a2023-07-041-3/+3
| | | |
| * | | try making CI fastertrinity-1686a2023-07-041-2/+4
|/ / /
* | | Merge branch 'bridge-pt-docs' into 'main'Alexander Færøy2023-07-035-8/+45
|\ \ \ | |/ / |/| | | | | | | | | | | | | | Additional documentation around bridges/PT configuration Closes #706 See merge request tpo/core/arti!1370
| * | Additional documentation around bridges/PT configurationNick Mathewson2023-07-034-7/+43
| | | | | | | | | | | | | | | | | | | | | This tries to flesh out some of the details for users who may be new to bridges and PTs. Closes #706.
| * | Finish a sentence in the documentation for TorClient::netdir()Nick Mathewson2023-07-031-1/+2
|/ /
* | Merge branch 'what-we-do-in-the-release-process' into 'main'Alexander Færøy2023-06-301-36/+196
|\ \ | |/ |/| | | | | | | | | Update Release.md to describe our current process Closes #942 See merge request tpo/core/arti!1366
| * Release.md: Add an extra semver-checks to the process.Nick Mathewson2023-06-301-0/+3
| | | | | | | | (We didn't do this previously, but it is a good idea.)
| * Release.md: Revise the release sectionsNick Mathewson2023-06-301-32/+21
| | | | | | | | | | | | | | | | * Remove instructions to sleep * Explain how to tag * Remind myself about the workaround for Fedora's delightful gpg/yubikey configuration. * Note that we should update "pages" till the blog post is up.
| * Release.md: document preparation sectionsNick Mathewson2023-06-301-13/+120
| | | | | | | | | | | | | | | | | | | | | | | | | | I've split this into "what I do in the days leading up to the release" and "what I do right before the release". There's a lot more detail now, including: * up-to-date invocations for `cargo upgrade` * up-to-date changelog instructions * our current version-bumping instructions * possible side-effects from version bumps.
| * Release.md: Write a tools section.Nick Mathewson2023-06-301-0/+18
| |
| * Release.md: Write the "are we ready to release" section.Nick Mathewson2023-06-301-3/+37
| | | | | | | | | | | | | | | | | | | | | | | | * Remove references to a couple of things that our CI now does for us (`cargo_audit` and `check_licenses`). * Mention ~Blocker issues and MRs. * Mention that some of our CI steps are allowed-to-fail, but failures should be examined. * Mention that some of our tools have exception lists that should get reviewed. * Mention `semver-checks` and `fixup-features`.
| * Release.md: Add subheadings for "how to release."Nick Mathewson2023-06-301-1/+10
|/
* Remove semver.md files for 1.1.6Nick Mathewson2023-06-3012-17/+0
|
* Merge branch 'keymgr-doc-fix' into 'main'arti-v1.1.6Nick Mathewson2023-06-301-2/+2
|\ | | | | | | | | keymgr: Fix broken doc link. See merge request tpo/core/arti!1363
| * keymgr: Fix broken doc link.Gabriela Moldovan2023-06-301-2/+2
|/
* Merge branch 'bump_versions_116' into 'main'Nick Mathewson2023-06-3046-251/+251
|\ | | | | | | | | Bump all versions in preparation for 1.1.6 release. See merge request tpo/core/arti!1362
| * Bump patchlevel versions on crates with smaller changesNick Mathewson2023-06-3035-186/+186
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ```