<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/doc/dev/notes, branch arti-v1.2.6</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.6</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.6'/>
<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: split "method not found"</title>
<updated>2024-07-25T12:43:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-23T13:43:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=aeb63c0085ae4bc26a74158c19992e1f256614c5'/>
<id>urn:sha1:aeb63c0085ae4bc26a74158c19992e1f256614c5</id>
<content type='text'>
We've wanted separate error codes for "no such method exists" and
"this method exists, but this object doesn't have it."
</content>
</entry>
<entry>
<title>Tests and documentation about NULs in the RPC stream.</title>
<updated>2024-07-16T13:51:27Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-11T16:54:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=35e46141af586c9fd25b90353cc06c17d207dd31'/>
<id>urn:sha1:35e46141af586c9fd25b90353cc06c17d207dd31</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc/dev/notes: vanguards: Make client rend circuits be STUB+.</title>
<updated>2024-06-25T16:30:16Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2024-06-25T16:30:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=72362be772dfdfdefde029c990a1f50656381baf'/>
<id>urn:sha1:72362be772dfdfdefde029c990a1f50656381baf</id>
<content type='text'>
According to the [vanguards spec], client rendezvous circuits should be
STUB+:
 * lite: `C -&gt; G -&gt; L2 -&gt; Rend`
 * full: `C -&gt; G -&gt; L2 -&gt; L3 -&gt; Rend`

[vanguards spec]: https://gitlab.torproject.org/tpo/core/torspec/-/blob/e5ace3667dcbbf893c6b632fd4e3f16114fd2a0e/spec/vanguards-spec/index.md
</content>
</entry>
<entry>
<title>relay-sketch: Add a link to 1454.</title>
<updated>2024-05-30T15:33:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-05-30T15:33:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=86038e2386177b44c1d0f609069edccd9a944b94'/>
<id>urn:sha1:86038e2386177b44c1d0f609069edccd9a944b94</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add ticket links to relay-sketch.md</title>
<updated>2024-05-30T15:26:12Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-05-30T15:26:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e7687accb01ad3753ae6e3b81267253ede37e7d1'/>
<id>urn:sha1:e7687accb01ad3753ae6e3b81267253ede37e7d1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>relay-sketch: Incorporate notes from Lisbon meeting.</title>
<updated>2024-05-30T12:20:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-05-30T12:19:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=022b3f97850e072ed8401e5e8a4f45736c896f47'/>
<id>urn:sha1:022b3f97850e072ed8401e5e8a4f45736c896f47</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-memtrack: Remove low-level part from memory-limit.md</title>
<updated>2024-04-23T15:09:27Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-04-16T19:15:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b4feaaab0922f57a10c3c70acb25113d23553780'/>
<id>urn:sha1:b4feaaab0922f57a10c3c70acb25113d23553780</id>
<content type='text'>
This part io now implemented.
</content>
</entry>
<entry>
<title>memtrack docs: Move overview to lib.rs</title>
<updated>2024-04-23T15:09:27Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-04-17T09:30:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1f72acb40725d2d7bddf1b2b441927b19e7d83e0'/>
<id>urn:sha1:1f72acb40725d2d7bddf1b2b441927b19e7d83e0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Sketch out first stages of work on relay support.</title>
<updated>2024-04-02T14:56:53Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-04-02T14:56:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9e4c084c9b1a4b36b0aabe0284dd8332ebdc4955'/>
<id>urn:sha1:9e4c084c9b1a4b36b0aabe0284dd8332ebdc4955</id>
<content type='text'>
@ahf asked me to try to outline what we should do in order to start
out here, so I'm putting this in.  It should cover us for a few
months.

This is by no means final; I'm just looking for initial comment.
</content>
</entry>
</feed>
