mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.1.0 2025-11-24T16:28:07Z 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-11-11T00:05:11Z Steven Engler opara@torproject.org 2025-11-10T23:55:46Z urn:sha1:a0b35d412b88285e6f7243818cbc5641e4778baf This gives us a consistent `listen()` implementation across runtimes, and gives us flexibility to customize the bind/listen process for TCP sockets. 2025-08-05T06:10:18Z Tobias Stoeckmann tobias@stoeckmann.org 2025-08-03T08:44:23Z urn:sha1:1623fd32272131c911ff53e8a2ea7b2516ffab07 Use unix-specific crates only if needed and suppress clippy warnings of unused variables if their usage is unix-specific. 2025-05-16T01:46:11Z Nick Mathewson nickm@torproject.org 2025-05-16T01:46:11Z urn:sha1:30617ad94bed7d2e4829c10144daf202d3ffd23c The `IoError::other` function is an easier way to say `IoError::new(IoErrorKind::Other, ...)`. It's been around since 1.74, but clippy started warning about the more verbose version in 1.87. 2025-03-24T13:58:54Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-03-06T15:52:03Z urn:sha1:73157920ffa84d6f1580170a0e40e5fbe3106a67 We change `NoUnixAddressSupport` to `NoAfUnixSocketSupport` because it doesn't make much sense to talk about support for the addresses separately from support for the sockets. 2025-03-24T13:58:54Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-03-06T15:16:03Z urn:sha1:a60165c11c66c579d628a670de56bfcff494c1cd 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: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`.