<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr/src, branch arti-v1.4.2</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.2</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.2'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-03-18T16:09:44Z</updated>
<entry>
<title>squash! Upgrade rand dependency to 0.9.</title>
<updated>2025-03-18T16:09:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-18T14:47:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=895bc807f106e359d35522a3ad5f288ba6cf6a9c'/>
<id>urn:sha1:895bc807f106e359d35522a3ad5f288ba6cf6a9c</id>
<content type='text'>
- The Rng::gen() functions have been renamed to Rng::random().
</content>
</entry>
<entry>
<title>squash! Upgrade rand dependency to 0.9.</title>
<updated>2025-03-18T16:09:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-18T13:01:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2f8993c22c2b86010e4fd8b5169ef0ab83f8c754'/>
<id>urn:sha1:2f8993c22c2b86010e4fd8b5169ef0ab83f8c754</id>
<content type='text'>
- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`
</content>
</entry>
<entry>
<title>netdoc: Make some parsing init functions fallible.</title>
<updated>2025-03-17T16:55:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-17T16:55:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f85cc0c663518edbe1c09ae2c6928e6f52cae7bb'/>
<id>urn:sha1:f85cc0c663518edbe1c09ae2c6928e6f52cae7bb</id>
<content type='text'>
I'm about to make our parsers reject some strings at construction
time, so it makes sense to have these functions become fallible.

This is a breaking change.
</content>
</entry>
<entry>
<title>tor-rtmock: allow-Decorate every use of MockSleepProvider</title>
<updated>2025-03-06T17:18:52Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-03-06T16:57:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a4054ed0d51e7c55946bde3c247190c9bbeef6fb'/>
<id>urn:sha1:a4054ed0d51e7c55946bde3c247190c9bbeef6fb</id>
<content type='text'>
MockSleepProvider and MockSleepRuntime have been declared deprecated
by the docs for some time.  We're about to mark them `#[deprecated]`.

This commit has been split out for clarity of review.
</content>
</entry>
<entry>
<title>tor-dirmgr: remove `dbg!`</title>
<updated>2025-03-05T22:27:11Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2025-03-05T22:27:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=35c45bf4d9fbfe86a3ac73665f2dfb6648a2e1f5'/>
<id>urn:sha1:35c45bf4d9fbfe86a3ac73665f2dfb6648a2e1f5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sqlite: Handle vanished blobs during consensus loading</title>
<updated>2025-03-05T17:56:59Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-04T15:51:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=79b8e4e1ecae606a104aa056a6e3c4be0c8d1d85'/>
<id>urn:sha1:79b8e4e1ecae606a104aa056a6e3c4be0c8d1d85</id>
<content type='text'>
Here we move the responsibility for removing ExtDoc entries for
vanished blobs into the _caller_ of read_blob(): we want to tidy all
such entries in one go.

Unlike a (reverted) previous approach, this time we don't need a
retry loop.
</content>
</entry>
<entry>
<title>sqlite: add a method to tidy extdocs for vanished blobs</title>
<updated>2025-03-05T17:56:59Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-05T15:05:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=82d888600ff9749ecd70a4e2214104a30f952385'/>
<id>urn:sha1:82d888600ff9749ecd70a4e2214104a30f952385</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sqlite.rs: Let read_blob signal whether it cleaned up.</title>
<updated>2025-03-05T17:56:59Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-04T15:32:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=193f07da9e96c31ce2e6df0944a9f33135b19e55'/>
<id>urn:sha1:193f07da9e96c31ce2e6df0944a9f33135b19e55</id>
<content type='text'>
We'll want to use this information to tell us whether to retry.
</content>
</entry>
<entry>
<title>sqlite: Extract body of latest_consensus into a new method</title>
<updated>2025-03-05T17:56:59Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-04T15:11:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1c8a60c415da5567ceb4249ced4662fd1318bac9'/>
<id>urn:sha1:1c8a60c415da5567ceb4249ced4662fd1318bac9</id>
<content type='text'>
I'm about to add a retry mechanism.
</content>
</entry>
<entry>
<title>sqlite: Stop ignoring any errors.</title>
<updated>2025-03-05T17:56:59Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-03-04T14:51:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7010167c848411149d038fdb675e7f720dc4a685'/>
<id>urn:sha1:7010167c848411149d038fdb675e7f720dc4a685</id>
<content type='text'>
We've already stopped ignoring any DB errors, so we may as well make
sure that any FS errors we encounter are also reported.
</content>
</entry>
</feed>
