<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr/src/storage, branch main</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=main</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-05-06T19:23:33Z</updated>
<entry>
<title>Remove users of fslock other than fslock-guard.</title>
<updated>2026-05-06T19:23:33Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-05-06T16:32:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=349316cfe9d5dae57ab44b65ffba11f425db5451'/>
<id>urn:sha1:349316cfe9d5dae57ab44b65ffba11f425db5451</id>
<content type='text'>
There were two that relied on the the ability to have a lock
in an unlocked state.  Instead, we replace those with
Option&lt;LockFileGuard&gt; or its equivalent.
</content>
</entry>
<entry>
<title>dirmgr: port to web-time-compat.</title>
<updated>2026-03-26T19:20:17Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-03-26T15:35:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=160ce5e616eb3c63b06f5b32f02b52bb248dbecc'/>
<id>urn:sha1:160ce5e616eb3c63b06f5b32f02b52bb248dbecc</id>
<content type='text'>
</content>
</entry>
<entry>
<title>dirmgr: Stub out usage of Lockfile on wasm32-unknown.</title>
<updated>2026-03-25T17:04:32Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-03-25T16:42:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=61bf683245d3098bb1a37ff75154f5e31933f0a5'/>
<id>urn:sha1:61bf683245d3098bb1a37ff75154f5e31933f0a5</id>
<content type='text'>
This is temporary while we wait on arti#2106.

(This made cargo-sort have me move a section around. Not sure why it
cares.)
</content>
</entry>
<entry>
<title>Fix word duplicate typos</title>
<updated>2026-03-15T20:18:56Z</updated>
<author>
<name>Tobias Stoeckmann</name>
<email>tobias@stoeckmann.org</email>
</author>
<published>2026-03-15T20:05:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2173207d8b909d1afdc55adda13faac13cdded0f'/>
<id>urn:sha1:2173207d8b909d1afdc55adda13faac13cdded0f</id>
<content type='text'>
</content>
</entry>
<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>
</feed>
