mirrors/arti.git/crates/arti-client/examples, branch arti-v2.0.0

Fix name of clippy lint to unchecked_time_subtraction (2)

2025-11-06T11:28:22Z

Run maint/add_warning

arti-client: Modified MSRV TODO for `once_cell` removal

2025-08-20T21:30:20Z

- Shortened the TODO added in a42413626abb57ad5610c8a73bfdd09ac68ac472 in the style of [this maintainer request] for consistency. [this maintainer request]: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2953#note_3197719 Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>

arti-client example: Write rather than hide an elided lifetime

2025-08-11T11:59:51Z

Fixes this warning. Not sure why it's not showing up in CI. --> crates/arti-client/examples/one_hop_circuit.rs:16:35 | 16 | fn find_one_hop_dir_cache(netdir: &NetDir) -> Option { | ^^^^^^^ ----- the same lifetime is hidden here | | | the lifetime is elided here | = help: the same lifetime is referred to in inconsistent ways, making the signature confusing = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default help: use `'_` for type paths | 16 | fn find_one_hop_dir_cache(netdir: &NetDir) -> Option> { | ++++

Switch Cargo.toml files to edition 2024.

2025-08-07T15:28:36Z

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.

Clippy 1.88 fix: reformat some debug prints.

2025-07-03T18:49:04Z

arti-client: Added TODO about replacing OnceCell

2025-04-18T02:39:17Z

- [`once_cell::sync::OnceCell`] should be replaced by [`std::sync::OnceLock`] once the blocking methods are stabilized and within our MSRV.

squash! Upgrade rand dependency to 0.9.

2025-03-18T16:09:44Z

- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`

tor-rtcompat: Add the ability to get a StreamOps handle.

2025-01-15T13:49:17Z

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: Require NetStream{Listener,Provider} streams to impl StreamOps (fmt).

2024-12-10T10:34:48Z

tor-rtcompat: Require NetStream{Listener,Provider} streams to impl StreamOps.

2024-12-10T10:34:48Z

Part of #1769