mirrors/arti.git/crates/tor-rtcompat/src, 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-15T13:49:17Z tor-rtcompat: Rename UnsupportedStreamOps to NoOpStreamOpsHandle (fmt). 2025-01-15T13:49:17Z Gabriela Moldovan gabi@torproject.org 2025-01-13T11:49:37Z urn:sha1:dc4fe47d5388074352ac00b561bed978779446e0 tor-rtcompat: Rename UnsupportedStreamOps to NoOpStreamOpsHandle. 2025-01-15T13:49:17Z Gabriela Moldovan gabi@torproject.org 2025-01-13T11:48:16Z urn:sha1:4ec53ca4dea324c2c170885d8556a67c802e491d This renames UnsupportedStreamOpsHandle to NoOpStreamOpsHandle for clarity (the old name kind of sounded like the name of an error type). tor-rtcompat: Fix doc warning. 2025-01-15T13:49:17Z Gabriela Moldovan gabi@torproject.org 2025-01-09T13:33:20Z urn:sha1:b900e8b9e874498b37bede2d91ef2abfe71f6921 tor-rtcompat: Big invasive change adding StreamOps bound everywhere. 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. tor-rtcompat: Implement StreamOps for TLS stream types. 2025-01-15T13:49:17Z Gabriela Moldovan gabi@torproject.org 2025-01-08T19:07:56Z urn:sha1:1569a9d0d224659158cb87586f8d2c65f28183b0 tor-rtcompat: Implement StreamOps for Framed. 2025-01-15T13:49:17Z Gabriela Moldovan gabi@torproject.org 2025-01-08T11:15:12Z urn:sha1:0f0bf7f68183608f27ef67b90a81b5687a3f7a35 tor-rtcompat: Implement new_handle() using TcpSockFd. 2025-01-15T13:49:17Z Gabriela Moldovan gabi@torproject.org 2025-01-08T19:35:08Z urn:sha1:f70ef5e04483c2d41f2efd98c9854e6447654bc6 tor-rtcompat: Add the ability to get a StreamOps handle. 2025-01-15T13:49:17Z Gabriela Moldovan gabi@torproject.org 2025-01-08T11:06:59Z urn:sha1:267235969df65d975b5deb01c342e1073d4c3847 Needed for cases where we wrap an object that implements `StreamOps` in an external type, thereby losing access to the `StreamOps` functionality. For example, during the channel handshake, we `.split()` the stream that implements `StreamOps`, which leaves us with a `SplitSink` and a `SplitStream`, neither of which implement `StreamOps`. Getting a handle to the underlying object that implements `StreamOps` (for example, a file handle) *before* the stream is `.split()` enables us to use `StreamOps` to manipulate the underlying split stream. This commit also introduces a special `UnsupportedStreamOpsHandle`, which is a type that implements `StreamOps`, but always returns an error. This type is meant to simplify error handling and usage, and is meant to be used in cases where `StreamOps` is not supported. TODO: the name of this type is pretty confusing (it's very similar to `UnsupportedStreamOp`, which is an error type), and should probably be renamed to something else (`NoOpStreamOpsHandle`, `BrokenStreamOpsHandle`, `DummyStreamOpsHandle` come to mind...). Note: this changes the `StreamOps` trait to be slightly different from what I originally envisioned in !2660 and #1769 tor-rtcompat: Note that SpawnBlocking isn't for CPU-bound tasks. 2025-01-07T18:27:14Z Wesley Aptekar-Cassels me@wesleyac.com 2025-01-07T16:21:59Z urn:sha1:d05dc32108ef6e11fde481024543cd943268ee8d 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.