mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.0 2026-06-08T16:56:56Z 2026-06-08T16:56:56Z Steven Engler opara@torproject.org 2026-06-02T03:11:16Z urn:sha1:44d92adfda6605c88a4b9af3cb10581f00a2c9f4 This hopefully better shows that there's nothing to use here for general socket types. 2026-06-08T16:55:27Z Steven Engler opara@torproject.org 2026-05-26T20:57:08Z urn:sha1:926c7a5449e29e2d652431a2406e7acae59bed50 This adds the trait type `ConnectOptions` to `NetStreamProvider` and adds this `ConnectOptions` as an argument to `NetStreamProvider::connect()`. You probably want to look at the changes in tor-rtcompat first, then the rest of this commit is updating the various places we use `NetStreamProvider`. 2026-05-07T15:05:57Z Steven Engler opara@torproject.org 2026-05-06T23:05:12Z urn:sha1:89790050b66f4eed80b9215b18c893ab7adba298 This adds the trait type `ListenOptions` to `NetStreamProvider` and adds this `ListenOptions` as an argument to `NetStreamProvider::listen()`. You probably want to look at the changes in tor-rtcompat first, then the rest of this commit is updating the various places we use `NetStreamProvider`. 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-08-07T15:28:36Z Nick Mathewson nickm@torproject.org 2025-08-06T01:19:58Z urn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc First, run ``` git grep -l "^edition =" | xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;' ``` Second, manually verify that all Cargo.toml files have changed, and nothing else has changed. Third, run cargo fmt again. 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 2024-12-19T21:12:25Z Nick Mathewson nickm@torproject.org 2024-12-11T19:41:25Z urn:sha1:61a8ec6f61caa6a1fa4ead15384d9a81553b1192 2024-12-10T10:34:48Z Gabriela Moldovan gabi@torproject.org 2024-12-05T15:02:12Z urn:sha1:bf7f5c8ea91357be2b2be366a91bee3d17ac5ecb Part of #1769 2024-12-10T10:34:48Z Gabriela Moldovan gabi@torproject.org 2024-12-05T15:00:11Z urn:sha1:56e9b79b09c65caee25a50c083fdd40f8c66f040 Part of #1769 2024-10-29T17:42:36Z Nick Mathewson nickm@torproject.org 2024-10-29T17:42:36Z urn:sha1:6239b036dcb041f6c7371fee824c3d65ec6f7d06