<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr/src/state.rs, branch tor-llcrypto-v0.4.4</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.4</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.4'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-02-09T12:56:18Z</updated>
<entry>
<title>tor-netdoc: Change fill_from_previous_netdir</title>
<updated>2023-02-09T12:56:18Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-02-01T13:15:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f69d7f96ac40dda53a8f4f6c01557195faaeff7c'/>
<id>urn:sha1:f69d7f96ac40dda53a8f4f6c01557195faaeff7c</id>
<content type='text'>
* Remove the return value, which was not used anywhere.
  Also remove the code to calculate the return value.

* Take an Arc&lt;NetDir&gt; rather than a reference.  We are going to want
  this for HS support.  This has no overall effect on the lifetime of
  the4 Arc, which was owned at the one call site and then imediately
  dropped.

* Change the documentation to explain what the function's role is in
  the netdir API, rather than the fiddly details of what it actually
  does internally.  Relegate the latter to a code comment.
  (When we have HS, this will do more, or, at least, make further
  arrangements.)
</content>
</entry>
<entry>
<title>Use ErrorReport - run rustfmt</title>
<updated>2023-01-30T18:52:32Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-01-30T18:51:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=37edcd688a63cd91a4652720d7d9fb66cc7efab1'/>
<id>urn:sha1:37edcd688a63cd91a4652720d7d9fb66cc7efab1</id>
<content type='text'>
Split off for ease of review and possible rebase.
</content>
</entry>
<entry>
<title>Use ErrorReport for errors in warn! in tor-dirmgr</title>
<updated>2023-01-30T18:52:32Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-01-30T18:19:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dc9352b5154f5902549781d89409430237d4ef9a'/>
<id>urn:sha1:dc9352b5154f5902549781d89409430237d4ef9a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Allow clippy::unchecked_duration_subtraction in tests</title>
<updated>2023-01-27T13:28:02Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-27T13:01:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a6dd92843edf2bd4c58de62a0d562921e4191ada'/>
<id>urn:sha1:a6dd92843edf2bd4c58de62a0d562921e4191ada</id>
<content type='text'>
This panics on error, and we're fine with a panic on misbehavior in
tests.
</content>
</entry>
<entry>
<title>Complete our migration to base64ct.</title>
<updated>2023-01-20T13:06:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-19T19:50:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=889206cde4ef29d7d10bda546f8ad518eb09c290'/>
<id>urn:sha1:889206cde4ef29d7d10bda546f8ad518eb09c290</id>
<content type='text'>
This is in lieu of upgrading to the latest base64 crate, which has
a different API from the old one.  Since we have to migrate either
way, we might as well use base64ct everywhere.

I don't think that most of these cases _require_ constant-time
base64, but it won't hurt.
</content>
</entry>
<entry>
<title>test lint blocks: Do some semi-manually</title>
<updated>2022-12-12T18:00:29Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-12-12T17:57:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=baf78361e848269a24a3019d99f87943872e6012'/>
<id>urn:sha1:baf78361e848269a24a3019d99f87943872e6012</id>
<content type='text'>
This is the hunks from running the rune in maint/adhoc-add-lint-blocks
but which require some subsequent manual fixup: usually, deleting
now-superfluous outer allows, but in some cases manually putting back
lints that the adhoc script deleted.
</content>
</entry>
<entry>
<title>Rename DirSkewTolerance to DirTolerance</title>
<updated>2022-07-22T14:04:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-22T14:04:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=41104137b12159d734f1171c1705c4e00f5244cd'/>
<id>urn:sha1:41104137b12159d734f1171c1705c4e00f5244cd</id>
<content type='text'>
This name is more accurate because we aren't only dealing with
clock skew here: we're also trying to tolerate the case where the
authorities fail to reach consensus for a while.
</content>
</entry>
<entry>
<title>Refactor most DirStatus users to use DirProgress.</title>
<updated>2022-06-13T16:22:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-13T16:22:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=68ea880b84c9aedfc276921675f94a257bcc2556'/>
<id>urn:sha1:68ea880b84c9aedfc276921675f94a257bcc2556</id>
<content type='text'>
This is all crate-internal APIs, fortunately.
</content>
</entry>
<entry>
<title>Rename DirStatusInner to DirProgress.</title>
<updated>2022-06-13T14:49:09Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-13T14:40:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f581feb0acff2d80aa825e4c187e62a2a2b61db2'/>
<id>urn:sha1:f581feb0acff2d80aa825e4c187e62a2a2b61db2</id>
<content type='text'>
This is about to become only a _part_ of what defines a DirStatus: a
DirStatus will also include a reset count, and some kind of info
about how long we've gone without progress.
</content>
</entry>
<entry>
<title>DirMgr:: Remove Error::NoChange as redundant.</title>
<updated>2022-05-25T12:58:37Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-25T12:58:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0caa5bcba5c3be8aca2fb90331a830d1a22f5e22'/>
<id>urn:sha1:0caa5bcba5c3be8aca2fb90331a830d1a22f5e22</id>
<content type='text'>
Now that the relevant functions now report changed/not-changed
status via a boolean out-parameter (see !527), there's no reason to
have a separate NoChanged error case.

Closes #484.
</content>
</entry>
</feed>
