<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-error/src, branch arti-v0.1.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.1.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.1.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-02-28T14:47:25Z</updated>
<entry>
<title>Fix typo in message</title>
<updated>2022-02-28T14:47:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-28T14:47:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ec25f68b9bf002034886256b18e6247b13a0018b'/>
<id>urn:sha1:ec25f68b9bf002034886256b18e6247b13a0018b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>EK::RemoteProtocolFailed replaces OtherRemote</title>
<updated>2022-02-28T13:27:44Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-02-28T13:27:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8898bbb4218b4858aabe80d5b049a8a025c1c7a9'/>
<id>urn:sha1:8898bbb4218b4858aabe80d5b049a8a025c1c7a9</id>
<content type='text'>
As per
  https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/355#note_2781816
</content>
</entry>
<entry>
<title>Introduce ErrorKind::OtherRemote</title>
<updated>2022-02-28T13:07:44Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-02-24T18:10:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c08a3170937c64d8cf699584867e5fe3fcc51fb6'/>
<id>urn:sha1:c08a3170937c64d8cf699584867e5fe3fcc51fb6</id>
<content type='text'>
arti-hyper wants to be able to have a kind for TLS failure.

Given that arti-hyper is above arti-client, this shows that callers
above arti-client might need to invent kinds for their own errors.

Possibly this means we need other Other errors for other locations.
If we have pluggable components we might even want OtherTorError.
</content>
</entry>
<entry>
<title>Merge branch 'proto_handshake_err' into 'main'</title>
<updated>2022-02-24T19:44:34Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-24T19:44:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7f3ea03e58dfe7a7dcc051aeb015b432cab876df'/>
<id>urn:sha1:7f3ea03e58dfe7a7dcc051aeb015b432cab876df</id>
<content type='text'>
tor-proto: Split up a couple of handshake-based errors

Closes #359 and #358

See merge request tpo/core/arti!344</content>
</entry>
<entry>
<title>tor-proto: Split IoErr  based on when it occurs</title>
<updated>2022-02-23T15:38:48Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-23T15:01:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=afa49eac8f45ea34a419e7a8cef7bb03026b5c75'/>
<id>urn:sha1:afa49eac8f45ea34a419e7a8cef7bb03026b5c75</id>
<content type='text'>
We want to distinguish handshake failures from errors later on in
the channel's lifetime.

Closes #359.
</content>
</entry>
<entry>
<title>Give specific error kinds to different END reasons</title>
<updated>2022-02-23T14:35:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-23T14:35:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6c615898e4789165f0ae67ff8f224f8ce2ead237'/>
<id>urn:sha1:6c615898e4789165f0ae67ff8f224f8ce2ead237</id>
<content type='text'>
Closes #360.
</content>
</entry>
<entry>
<title>Cleanups on !340 from @diziet</title>
<updated>2022-02-23T13:17:27Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2022-02-23T13:17:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=05bf12edfa5f9945bf20c6e2b50390c1e34e40a8'/>
<id>urn:sha1:05bf12edfa5f9945bf20c6e2b50390c1e34e40a8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Make NoLock into BadApiUsage.</title>
<updated>2022-02-22T21:13:37Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-22T21:13:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=784f1531bbf9c93f60d53249197c9e98a6977d26'/>
<id>urn:sha1:784f1531bbf9c93f60d53249197c9e98a6977d26</id>
<content type='text'>
To implement this, we had to refactor the tor_circmgr api for
flushing state changes to disk, so that it checks if it has the lock,
and only then tries to store.
</content>
</entry>
<entry>
<title>Eliminate RequestedResourceAbsent kind.</title>
<updated>2022-02-22T21:00:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-22T21:00:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a2e2663e90df6a10d5f4d4b28d7070f26f04cf24'/>
<id>urn:sha1:a2e2663e90df6a10d5f4d4b28d7070f26f04cf24</id>
<content type='text'>
There was only one use of this, and it was in as-yet-unused relay-only
code.

Removing this type required refactoring the relay onion handshake code
to use its own error type, which is probably clever anyway.
</content>
</entry>
<entry>
<title>Fold NamespaceFull into BadApiUsage.</title>
<updated>2022-02-22T20:44:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-22T20:44:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=789e6c87b83484fd8ad118e9f00965da31ede954'/>
<id>urn:sha1:789e6c87b83484fd8ad118e9f00965da31ede954</id>
<content type='text'>
</content>
</entry>
</feed>
