<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-rpcbase/README.md, branch arti-v2.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-v2.5.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-07-25T12:46:29Z</updated>
<entry>
<title>rpc: Remove RpcError data field and use Report</title>
<updated>2024-07-25T12:46:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-23T17:26:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2e9cc83fd918a40f551bcc3f9595956067044aad'/>
<id>urn:sha1:2e9cc83fd918a40f551bcc3f9595956067044aad</id>
<content type='text'>
Per discussion, this field isn't really specified in a way that lets
us fill it sensibly at the moment.  So for now, we're going to just
omit it.

Additionally, we said that we'd Report on our errors; this branch
changes the implementation of RpcError to do that.

Question: Will the blanket implementation for Into&lt;RpcError&gt; make
it harder to re-add a Data field later on if we want to do so?
</content>
</entry>
<entry>
<title>rpc: Refactor errors part 1: a new RpcMethod trait.</title>
<updated>2024-07-25T12:43:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-23T17:23:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c7c630c44d9e937d7185f591d75fd42c33ab5238'/>
<id>urn:sha1:c7c630c44d9e937d7185f591d75fd42c33ab5238</id>
<content type='text'>
It is no longer necessary to say, for every RPC method,
that its error type is RpcError.
</content>
</entry>
<entry>
<title>rpcbase: Replace a TODO with a set of notes and caveats</title>
<updated>2024-07-25T12:43:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-23T14:20:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=593e0dfbc0da6ef4d3ed6e403122b178432eb571'/>
<id>urn:sha1:593e0dfbc0da6ef4d3ed6e403122b178432eb571</id>
<content type='text'>
We have decided not to remove the "anybody can define methods"
property.  This commit documents the consequences, and warns
extenders away from some really bad ideas.
</content>
</entry>
<entry>
<title>Write a README for tor-rpcbase</title>
<updated>2024-06-24T13:12:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-06-20T00:38:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ed09f1d0d0cac2670244f1752f771372d8353599'/>
<id>urn:sha1:ed09f1d0d0cac2670244f1752f771372d8353599</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rename tor-rpccmd to tor-rpcbase.</title>
<updated>2023-04-12T11:34:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-04-11T19:13:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9a5f319a840bbbd906d64803a4992ea1e21b7d1f'/>
<id>urn:sha1:9a5f319a840bbbd906d64803a4992ea1e21b7d1f</id>
<content type='text'>
</content>
</entry>
</feed>
