mirrors/arti.git/crates/tor-rtmock/src/task.rs, branch arti-v1.4.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.0 2025-01-30T08:39:30Z fix: fix typos 2025-01-30T08:39:30Z Dimitris Apostolou dimitris.apostolou@icloud.com 2025-01-30T08:39:30Z urn:sha1:6371829c976f6a5b77d46bf977f369a915f2ced3 tor-rtmock: drop_reentrancy test: Run under miri too 2025-01-15T10:34:20Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-01-07T14:33:41Z urn:sha1:eca4022290285850360d52af5eca1b3a37b6816d tor-rtmock: Explicitly manage the lifetime of the future 2025-01-15T10:34:07Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-01-02T15:47:55Z urn:sha1:ae4ede76614985a19a3245bbc4cfc7e6a6340b84 Previously, if r is Pending, `fut` is moved out of (stored in `task.fut`), whereas if r is Ready, it is retained and then dropped at the end of the loop iteration. This is quite subtle, and involves `fut` being in a "maybe moved out of" state (which cannot be represented in Rust's surface type system) after the block with the `data` lock. Let's write code that more clearly ensures that the compiler DTRT. tor-rtmock: Add a test case for Future drop entrancy 2025-01-15T10:34:06Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-01-02T16:11:25Z urn:sha1:11699a9da14098cf8212a95de66ac2a0e0bae25c This passes right now, but only because the lifetime of the `fut` variable in `execute_until_first_stall` happens to be right. tor-rtmock: Avoid misleading task dumps by careful drop sequencing 2025-01-15T10:33:18Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-01-02T16:16:35Z urn:sha1:97db02abf3681a7baa49463549baffae6143e9ed tor-rtmock: Add some more tracing / debug output 2025-01-15T10:33:18Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-12-18T14:43:30Z urn:sha1:99f1ba647f08b20e7576a619c0333ad7f6f030d9 tor-rtmock: Explain a difficulty with test trace output 2025-01-15T10:33:18Z Ian Jackson ijackson@chiark.greenend.org.uk 2024-12-18T14:39:37Z urn:sha1:ab1399d100a9ac75804d605fa4841955476520eb tor-rtcompat: Use GAT instead of RPIT in SpawnBlocking trait. 2025-01-07T18:27:14Z Wesley Aptekar-Cassels me@wesleyac.com 2024-12-19T19:30:29Z urn:sha1:665d3145a0db86bd1fbd7549b64e21a160c45ff1 Due to the limitations on RPIT, it's better to use a GAT for now. tor-rtmock: Add task names for spawn_obj and spawn_blocking. 2025-01-07T18:26:28Z Wesley Aptekar-Cassels me@wesleyac.com 2024-12-19T18:30:57Z urn:sha1:a7b0f5baab504ec16eb0b8b32b7f8f78c97d1366 tor-rtcompat: Add spawn_blocking to Runtime trait. 2025-01-07T18:26:28Z Wesley Aptekar-Cassels me@wesleyac.com 2024-12-18T20:57:30Z urn:sha1:5f91a2b5fa6f343a51cc325ee7a9519f7523d14c This adds a new SpawnBlocking trait, which exposes the spawn_blocking function that tokio, async-std, and other runtimes have.