<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr/src, branch arti-v1.1.3</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.3</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.3'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-03-21T13:08:14Z</updated>
<entry>
<title>Sort out some TODOs in bdtest.rs</title>
<updated>2023-03-21T13:08:14Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-03-21T12:10:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d24a47c1d9b3793b8f2b0f456c17b013724d6e50'/>
<id>urn:sha1:d24a47c1d9b3793b8f2b0f456c17b013724d6e50</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix a bunch of needless-conversion warnings.</title>
<updated>2023-03-10T12:09:50Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-03-10T12:03:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=552acbf07fac3c3c9c431caeea128c903b0bf557'/>
<id>urn:sha1:552acbf07fac3c3c9c431caeea128c903b0bf557</id>
<content type='text'>
Apparently 1.68 now warns when you call into_iter() on something
that's already an iterator.  Fair enough.  Let's stop doing that.
</content>
</entry>
<entry>
<title>tor-dirmgr: Don't try to mark consensus usable in a read-only store.</title>
<updated>2023-03-08T12:08:17Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-03-08T12:08:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ac5469d0b6eeecd3fe73d561f7f0602f67749796'/>
<id>urn:sha1:ac5469d0b6eeecd3fe73d561f7f0602f67749796</id>
<content type='text'>
Doing this means that any attempt to use a read-only store would
crash as soon as it found that the consensus was usable.

It seems that this bug was introduced at some point doing all the
dirmgr refactors we did over the past year.  Perhaps there should be
a test for running with a read-only store.

Fixes #779
</content>
</entry>
<entry>
<title>tor-dirmgr: Work around an apparent regression in `time`.</title>
<updated>2023-02-17T19:36:19Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-02-17T19:24:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2b515c8d257586f1cd6bc6c74a61ed0de60aab4f'/>
<id>urn:sha1:2b515c8d257586f1cd6bc6c74a61ed0de60aab4f</id>
<content type='text'>
Some code in our tests that worked fine with time 0.3.17 no
longer works with 0.3.19, despite the semver.

See https://github.com/time-rs/time/issues/552 for the upstream bug.
</content>
</entry>
<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's .report() for two errors in error! in bridgedesc.rs</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:48:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=aa7397bc0f43f67f42ed7f2e8dbe2ecdbf302058'/>
<id>urn:sha1:aa7397bc0f43f67f42ed7f2e8dbe2ecdbf302058</id>
<content type='text'>
No functional change, just using the new idiom.
</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>Use ErrorReport for errors in info! in tor-dirmgr</title>
<updated>2023-01-30T18:04:57Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-01-30T18:04:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cc6cf7f973f3750a86c456426a7f0c46acb619f2'/>
<id>urn:sha1:cc6cf7f973f3750a86c456426a7f0c46acb619f2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>"Fix" remaining unchecked-subtraction warnings.</title>
<updated>2023-01-27T14:16:41Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-27T13:20:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2127c6b0883cfeedb92c1c88ccff59d63acd22a5'/>
<id>urn:sha1:2127c6b0883cfeedb92c1c88ccff59d63acd22a5</id>
<content type='text'>
In both cases I think it's fine to panic; but it's best to do so
explicitly.
</content>
</entry>
</feed>
