<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr/src/storage, branch arti-v2.0.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.0.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.0.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-12-01T12:36:13Z</updated>
<entry>
<title>dirmgr: Rewrite .is_some()/.unwrap() using let match</title>
<updated>2025-12-01T12:36:13Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2025-12-01T11:05:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c7bd6f06a510c17b5831bdacbd981c37ba924380'/>
<id>urn:sha1:c7bd6f06a510c17b5831bdacbd981c37ba924380</id>
<content type='text'>
On nightly, clippy now warns against this and recommends using a `match`
instead.

See https://rust-lang.github.io/rust-clippy/master/index.html#unnecessary_unwrap
</content>
</entry>
<entry>
<title>Switch Cargo.toml files to edition 2024.</title>
<updated>2025-08-07T15:28:36Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-08-06T01:19:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=77b0de43b8c67cdb81befe0680a3df43b6ad37bc'/>
<id>urn:sha1:77b0de43b8c67cdb81befe0680a3df43b6ad37bc</id>
<content type='text'>
First, run

```
git grep -l "^edition =" |
    xargs perl -i -pe 's/^edition *=.*/edition = "2024"/;'
```

Second, manually verify that all Cargo.toml files have changed,
and nothing else has changed.

Third, run cargo fmt again.
</content>
</entry>
<entry>
<title>dirmgr, netdir: Store protocol requirments as soon as they are validated.</title>
<updated>2025-04-16T23:06:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-04-03T15:20:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=98f28d0b4c5c2b90ed732ed29d571f71a48c15b4'/>
<id>urn:sha1:98f28d0b4c5c2b90ed732ed29d571f71a48c15b4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>dirmgr: Backend support for cacheing protocol status.</title>
<updated>2025-04-16T23:06:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-04-03T12:47:41Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b483b454669b8b0ce93ea52896992d9234e4779d'/>
<id>urn:sha1:b483b454669b8b0ce93ea52896992d9234e4779d</id>
<content type='text'>
We want to store this separately from the consensus,
because we want to access it very early in our load-from-cache
process, without checking the consensus that contains it
for timeliness.
</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>
