<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-rpc-client-core/src/ffi, branch arti-v1.5.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.5.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-08-07T15:28:39Z</updated>
<entry>
<title>Fix warnings and errors from edition 2024.</title>
<updated>2025-08-07T15:28:39Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-06T01:54:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4fbbffe7c14b2df6290268b6e3c8530106ab2529'/>
<id>urn:sha1:4fbbffe7c14b2df6290268b6e3c8530106ab2529</id>
<content type='text'>
The two main causes of errors were:

- Since some of the lifetime rules have changed, we no longer need
  to do as many "bind a variable and immediately return it"
  patterns, and so clippy now warns about them.
- We needed to adjust the explicit captures (`use&lt;...&gt;`)
  in a couple of our RPIT instances.
</content>
</entry>
<entry>
<title>Switch Cargo.toml files to edition 2024.</title>
<updated>2025-08-07T15:28:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-06T01:19:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=77b0de43b8c67cdb81befe0680a3df43b6ad37bc'/>
<id>urn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>fix `clippy::doc_overindented_list_items`</title>
<updated>2025-04-03T17:32:58Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-04-03T17:21:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=663339ffa8bd00ce59c2dd39c288d338505263c3'/>
<id>urn:sha1:663339ffa8bd00ce59c2dd39c288d338505263c3</id>
<content type='text'>
Example:

```text
warning: doc list item overindented
   --&gt; crates/arti-rpc-client-core/src/conn/connimpl.rs:322:9
    |
322 |     ///    indicates that no more messages will be received for this request.
    |         ^^^ help: try using `  ` (2 spaces)
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
note: the lint level is defined here
   --&gt; crates/arti-rpc-client-core/src/lib.rs:8:9
    |
8   | #![warn(clippy::all)]
    |         ^^^^^^^^^^^
    = note: `#[warn(clippy::doc_overindented_list_items)]` implied by `#[warn(clippy::all)]`
```
</content>
</entry>
<entry>
<title>AF_UNIX terminology: Rename two error variants</title>
<updated>2025-03-24T13:58:54Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-03-06T15:20:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0f588e4bb3899521cd6d7ef4f4d10445e900f80a'/>
<id>urn:sha1:0f588e4bb3899521cd6d7ef4f4d10445e900f80a</id>
<content type='text'>
Change `..UnixAddress...` to `...AfUnixAddress..`.
</content>
</entry>
<entry>
<title>RPC: Abolish an unused and misnamed error variant</title>
<updated>2025-03-24T13:58:54Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-03-06T15:41:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4bc9e6c47dcd764b5d95a47b66fd27167458c8a8'/>
<id>urn:sha1:4bc9e6c47dcd764b5d95a47b66fd27167458c8a8</id>
<content type='text'>
This variant breaches the new guidelines about AF_UNIX terminology.
And its purpose is unclear and it's not used.
</content>
</entry>
<entry>
<title>rpclib: Improve output for ConnectFailure</title>
<updated>2025-02-04T19:41:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-02-04T17:28:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dffe9330ab57d90f844f2aac950e4cbc2fc7a70b'/>
<id>urn:sha1:dffe9330ab57d90f844f2aac950e4cbc2fc7a70b</id>
<content type='text'>
We want to explain better what has happened, not only with the final
fatal error, but with any nonfatal errors that occurred in the middle.

Closes #1826.
</content>
</entry>
<entry>
<title>rpclib: Include sources when formatting FFI errors.</title>
<updated>2025-02-04T19:41:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-02-04T15:40:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=921ae4c6cea7893aae854e562720310388b8897b'/>
<id>urn:sha1:921ae4c6cea7893aae854e562720310388b8897b</id>
<content type='text'>
Closes #1650.
</content>
</entry>
<entry>
<title>rpclib: New combined error type for RPC connect failures.</title>
<updated>2025-01-29T14:17:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-28T14:52:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=28cc171b91d315412286b52297e0973fd2431f41'/>
<id>urn:sha1:28cc171b91d315412286b52297e0973fd2431f41</id>
<content type='text'>
This type explains where every error came from, and explains why
each declined connect point was declined.
</content>
</entry>
<entry>
<title>arti-rpc-client-core: Rename Authentication{Rejected=&gt;Failed}</title>
<updated>2025-01-23T18:06:23Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-23T17:37:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2d4872c41eec4d4ec27f022ede306b68d1583492'/>
<id>urn:sha1:2d4872c41eec4d4ec27f022ede306b68d1583492</id>
<content type='text'>
Also change corresponding message.

This way, it will be clear that we're just reporting that Arti
gave us an error—not that the error necessarily means that the
authentication itself was "wrong".
</content>
</entry>
<entry>
<title>rpclib: Avoid overuse of execute_internal_ok.</title>
<updated>2025-01-23T18:06:23Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-01-22T17:31:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0d9ebbfacb4636597f661f89bfc5f24975aa7cb7'/>
<id>urn:sha1:0d9ebbfacb4636597f661f89bfc5f24975aa7cb7</id>
<content type='text'>
The execute_internal_ok method converts every error response into an
internal error; as such, it's only appropriate when there is no way
for a well-behaved Arti instance to give an error response.
But we had been using it in a few places where errors were possible
under other circumstances.

This commit fixes that behavior, and adds documentation to help
avoid it.
</content>
</entry>
</feed>
