mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.1.0 2026-01-29T17:56:18Z 2026-01-29T17:56:18Z Nick Mathewson nickm@torproject.org 2026-01-27T17:28:57Z urn:sha1:bc856a46856d7585cdf6474e7f491b51afeffa1f These are as yet unimplemented; there's a stub type for the providers (nativetls) that won't actually have them. 2025-11-24T16:28:07Z Wesley Aptekar-Cassels me@wesleyac.com 2025-11-24T16:28:07Z urn:sha1:a4db6a7495b13dd7b00416dd1660a5ad82b60919 These are all aimed at figuring out in more detail what's going on in #2079 and related issues. 2025-04-09T16:52:03Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-04-07T16:58:45Z urn:sha1:2a7dc6c46274e0d96e773c031cabd5373483429e The future no longer needs to be `Send + 'static`. 2025-03-04T17:33:25Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-03-04T15:39:48Z urn:sha1:11049b07c419fc7544c382a98ea8366d6b468daf Let's use Tokio terminology here. 2025-03-04T17:30:43Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-26T16:10:04Z urn:sha1:d7d8affb67e8009257dca1b4ef05117de364bd66 This member is the principal one which implemnets Spawn, Blocking and perhaps ToplevelBlockOn. It doesn't appear that we actually need to split this into multiple members. 2025-03-04T17:30:43Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-26T16:03:32Z urn:sha1:9a491ce278bb581405aecd5dbef36d0f4aef1198 This was referenced and explained from the docs, but didn't exist yet. Here it is. Everyone except the Tokio glue, and the CompoundRuntime, just use the default implementation in terms of spawn_thread. spawn_thread has a more relaxed contract, so this is correct. 2025-03-04T17:30:43Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-26T16:03:43Z urn:sha1:878c32bc1e9027fa3cf405c87f5323b94969b0fb Forbid re-entering the executor using ToplevelBlockOn::block_on. This was always forbidden in the case of MockExecutor, but that meant that tests using MockExecutor would malfunction if the code under test needed to re-enter the executor from sync code (since the code under test would have to use block_on, which wrong). See #1835. Provide a function which *can* do this, reenter_block_on. The MockExecutor needs to know the difference, and other runtimes may too. They are conceptually quite different operations. Introduce ToplevelRuntime as a convenience alias. 2025-03-04T17:30:43Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-25T14:10:35Z urn:sha1:20eabfcc81a2d0df61ce297b28c7412c3ceab7fd * Document the new plan for blocking interaction in the trait-level docs for the Blocking trait (used to be SpawnBlocking). Add cross-references (in some cases to not-yet-existing pieces). * Rename: spawn_blocking to spawn_thread. We're going to distinguish thread-creation (relatively expensive) from brief entry to sync code (relatively cheap, but more restricted). * Rename the SpawnBlocking trait to Blocking, and its ThreadHandle to ThreadHandle. This trait is going to gain more functionality. * Add the missing mention of `Blocking` to the docs for `Runtime`. 2025-03-04T17:30:43Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-13T17:39:39Z urn:sha1:849558047071897b9bbdbdd28d06d15b52b3af10 We're going to distinguish top-level runtime entry, from *re*-entry to an existing executor. It is most convenient to rename this trait first. Documentation of the distinction will come later. (We're going to retain the function name `block_on`, but we want the trait to be more obviously a top-level only thing, though, so we give it a name that will hopefully avoid it peroulating throughout the codebase..) 2025-01-15T13:49:17Z Gabriela Moldovan gabi@torproject.org 2025-01-08T19:08:57Z urn:sha1:f04709c16d0ebf039779c404cf0c907f13965852 This is unfortunately necessary, because after the channel handshake, we need to give the channel reactor a `StreamOps` handle to the underlying stream.