<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-error/src/lib.rs, branch arti-v1.2.8</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.8</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.8'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-09-25T14:37:18Z</updated>
<entry>
<title>Upgrade to derive_more version 1.0.0</title>
<updated>2024-09-25T14:37:18Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-25T14:37:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6a12c2ba8515226a772d5f4a81930bf42d67535a'/>
<id>urn:sha1:6a12c2ba8515226a772d5f4a81930bf42d67535a</id>
<content type='text'>
The `derive_more` crate broke backward compatibility with this version,
so this change involved quite a few manual fixups.
With luck, they'll keep compatibility for some while in the future.
</content>
</entry>
<entry>
<title>tor-error: implement HasKind on void::Void and Infallible.</title>
<updated>2024-08-13T00:27:03Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-08-12T16:31:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ef6f70c2cf6b947d6f42efb630e04721442dfe4d'/>
<id>urn:sha1:ef6f70c2cf6b947d6f42efb630e04721442dfe4d</id>
<content type='text'>
`void::Void` represents the type of an object that can't be
constructed.  It's especially useful as the error type of an
infallible function.  `void::Void` already implements
`std::error::Error`, so all we need to do to use it as a "can't
happen" error type in our code is to have it also implement
`HasKind`.

Also implement HasKind for Infallible while we're at it.
</content>
</entry>
<entry>
<title>rpc: Rename the error codes for something like consistency.</title>
<updated>2024-07-25T12:46:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-07-24T18:51:54Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=847e80f307789c607ac3415254b292e20da9c7f0'/>
<id>urn:sha1:847e80f307789c607ac3415254b292e20da9c7f0</id>
<content type='text'>
</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>Re-run maint/add_warning.</title>
<updated>2024-05-06T13:31:35Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-05-06T13:23:41Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=97f452ec9958bf7d8ca3275c39655814a4494637'/>
<id>urn:sha1:97f452ec9958bf7d8ca3275c39655814a4494637</id>
<content type='text'>
This commit is automatically generated.
</content>
</entry>
<entry>
<title>tor-error: Fix message for LocalResourceExhausted</title>
<updated>2024-04-23T15:09:27Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-04-23T14:49:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=418844ac6a413fb12e682c45bc9fbc9a6b2ded4b'/>
<id>urn:sha1:418844ac6a413fb12e682c45bc9fbc9a6b2ded4b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-error: Add ErrorKind::LocalResourceExhausted</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:10:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f04513b636c1b4a44d6bcbb8654fe0f7c1134d33'/>
<id>urn:sha1:f04513b636c1b4a44d6bcbb8654fe0f7c1134d33</id>
<content type='text'>
</content>
</entry>
<entry>
<title>deny clippy::unchecked_duration_subtraction</title>
<updated>2024-02-29T17:16:49Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2024-02-29T17:06:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ac5b36027ca825d27ef466501c660ce498fd9e3c'/>
<id>urn:sha1:ac5b36027ca825d27ef466501c660ce498fd9e3c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-error: ErrorReport: seal</title>
<updated>2023-12-12T12:52:41Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-12-12T12:40:26Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=00903e22bb9782958135a7061dcfb523e4ebc91f'/>
<id>urn:sha1:00903e22bb9782958135a7061dcfb523e4ebc91f</id>
<content type='text'>
We're going to need to make change to this trait which would be
breaking for out-of-crate implementors.  This should have been sealed
all along.
</content>
</entry>
<entry>
<title>tor-error: Introduce ErrorKind::LocalResourceAlreadyInUse</title>
<updated>2023-12-11T15:30:50Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-11-22T14:07:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=99e58a0792df855609f96728d43742f8e07e2132'/>
<id>urn:sha1:99e58a0792df855609f96728d43742f8e07e2132</id>
<content type='text'>
Our HSS code isn't going to work if you run more than one copy.  Soon
we'll detect this (via our use of tor_persist).

There may be other places this ought to be used.  Eg if we get
EADDRINUSE from trying to set up a proxy, maybe ...
</content>
</entry>
</feed>
