mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.0.0 2025-03-04T17:30:43Z 2025-03-04T17:30:43Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-26T15:30:53Z urn:sha1:5618b0367a5eb25c03f71a36b9ef625cdfa08be1 Introduce ToplevelRuntime as an alias, and use it in the top-level programs. Now none of the principal protocol implementation code has access to the executor's toplevel entrypoint, and can't call it by mistake. 2024-04-03T12:11:39Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-04-02T11:58:49Z urn:sha1:b71d0bf6cd413650550b40ce81e02dc47ae2fa5e This is the combination of a number of separate commits, many of which were generated by seddery, and then rebased and squashed. Cargo.toml perl -i~ -pe 's{^derive-adhoc}{derive-deftly = "0.10"}' crates/*/Cargo.toml (not regenerated during rebase) update Cargo.lock `cargo fetch` without --locked (regenerated during rebase) seddery git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{^use derive_adhoc}{use derive_deftly}' git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bdefine_derive_adhoc\b}{define_derive_deftly}g' git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bAdhoc\b}{Deftly}g if m{derive}' git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\#\[derive_adhoc\b}{#[derive_deftly}g' git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{use derive_adhoc}{use derive_deftly}' git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bderive_adhoc\b}{derive_deftly_adhoc} if m{use.*deftly}' git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bderive_adhoc!}{derive_deftly_adhoc!}' (not regenerated during rebase) Manually add `#[derive_deftly_adhoc]` where needed. seddery git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\#\[adhoc\b}{#[deftly}g' git-ls-files | grep '\.rs$' | xargs perl -i~ -pe 's{\bderive_adhoc_template}{derive_deftly_template}' (not regenerated during rebase) Manually fix up an import Manually update some builder attrs Manually fix up tor_rtmock::time_core This was missed in my seddery, due to me rebasing the branch and not redoing the seddery. 2023-07-07T09:26:44Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-06T14:46:35Z urn:sha1:6e495d8400e9e5b0deb087d572f821d7fd802b8f 2023-07-06T14:58:42Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-06T14:34:24Z urn:sha1:f0168b5220b47ea5563893d0e57f2b26a1c3be61 These are always the same and probably always will be. 2023-07-06T14:14:40Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-05T11:28:41Z urn:sha1:395a616c9f1a513c2905548aa13d5345cd1b937c 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. 2023-07-06T14:14:40Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-05T10:01:05Z urn:sha1:492699d52207001fd9eb2bf9bfb6899e47c01234 This deduplicates some imports, which would otherwise be about to become triplicated. 2023-07-06T14:14:40Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-07-04T15:17:18Z urn:sha1:97e817b330853e468268a6b43a310d7e305bd989 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. 2022-05-11T12:26:35Z eta tor@eta.st 2022-05-11T12:26:35Z urn:sha1:864fd03917a0409c6a0380c258d96252359a559b - arti#445 highlighted the lack of good documentation around Arti's multiple runtime support, as well as it being difficult to determine what runtime was actually in use. - Improve the documentation to solve the first problem. - To solve the second problem, make Runtime require Debug (which is arguably a good idea anyway, since it makes them easier to embed in things), and print out the current runtime's Debug information when arti is invoked with `--version`. - (It also prints out other Cargo features, too!) fixes arti#445 2022-03-14T19:59:33Z trinity-1686a trinity@deuxfleurs.fr 2022-03-05T18:49:38Z urn:sha1:4a44ef56c0743775d49eca138a253f11e93c7a35 2022-01-26T19:06:58Z Nick Mathewson nickm@torproject.org 2022-01-26T18:59:37Z urn:sha1:bf8fa66d36298561cc868706f748049cec23f5eb This avoids a future confusion with the new `SpawnBlocking` trait in async_executors v0.5, and better describes what the trait provides.