<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr/src/bootstrap.rs, branch arti-v1.4.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.4.3</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.3'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2025-04-16T23:06:51Z</updated>
<entry>
<title>dirmgr: Always apply changes before advancing consensus.</title>
<updated>2025-04-16T23:06:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2025-04-08T18:14:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=69f656c017b8ce7d804bc65dd1dac24b3aa94427'/>
<id>urn:sha1:69f656c017b8ce7d804bc65dd1dac24b3aa94427</id>
<content type='text'>
In the directory code, we have functionality to advance the
consensus download state whenever possible, even if there is more we
could download in the current state.

That's fine, but when we're in this position, we need to be sure
that we're taking any action based on the current state (such as
installing notably parameters or, notably, protocol recommendations)
before we move on.
</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>Upgrade to derive_more version 1.0.0</title>
<updated>2024-09-25T14:37:18Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-25T14:37:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6a12c2ba8515226a772d5f4a81930bf42d67535a'/>
<id>urn:sha1:6a12c2ba8515226a772d5f4a81930bf42d67535a</id>
<content type='text'>
The `derive_more` crate broke backward compatibility with this version,
so this change involved quite a few manual fixups.
With luck, they'll keep compatibility for some while in the future.
</content>
</entry>
<entry>
<title>extract tor_async_utils::oneshot into ::oneshot-fused-workaround</title>
<updated>2024-08-28T14:27:46Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2024-08-22T19:20:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=46f7f01092e6ac55e3e958dc3a2228b1d36e26a1'/>
<id>urn:sha1:46f7f01092e6ac55e3e958dc3a2228b1d36e26a1</id>
<content type='text'>
Having this in the `tor-async-utils` crate prevents us from doing both
of the following without introducing a circular dependency:

* using it in `tor-rtmock` (which we currently do, particularly in
  tests).
* using `tor-rtmock` to test things in `tor-async-utils`. We don't do
  this yet, but it is generally sensible to do so. In particular we
  want to move the `stream_peak` module there, which is currently tested
  with `tor-rtmock`.

Moving this into its own crate avoids this circular dependency.
</content>
</entry>
<entry>
<title>dirmgr: Limit the number of mds that we will fetch from sqlite at once.</title>
<updated>2024-06-12T16:48:27Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-06-12T16:48:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=efed73632bfb45ce2300c81b2d5b9f8ed356535e'/>
<id>urn:sha1:efed73632bfb45ce2300c81b2d5b9f8ed356535e</id>
<content type='text'>
This should help limit our memory usage when restarting from cache.

Possible (imperfect) solution for #1027.
</content>
</entry>
<entry>
<title>dirmgr: split out the loading part of load_once into a new function.</title>
<updated>2024-06-12T16:43:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-06-12T16:43:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=54317e23971bcfa079df6eb70ef7017b1204e5b9'/>
<id>urn:sha1:54317e23971bcfa079df6eb70ef7017b1204e5b9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>properly report bootstrap readiness without cache</title>
<updated>2024-04-29T15:45:59Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2024-04-29T15:45:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0cd0e314b5dbd3ea523ccfbe3927064e48e2c251'/>
<id>urn:sha1:0cd0e314b5dbd3ea523ccfbe3927064e48e2c251</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Run maint/add_warning.</title>
<updated>2024-03-13T16:30:53Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-03-13T16:30:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c0c9bd15d42897825dd0ab3d3b8dd1c17bd6320c'/>
<id>urn:sha1:c0c9bd15d42897825dd0ab3d3b8dd1c17bd6320c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>clippy: Use Result::cloned in several places</title>
<updated>2024-01-31T14:35:58Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-01-31T14:27:47Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6fbc7e0ab48c5a424d13944f1103f18e3ec33913'/>
<id>urn:sha1:6fbc7e0ab48c5a424d13944f1103f18e3ec33913</id>
<content type='text'>
</content>
</entry>
<entry>
<title>oneshot: Apply deferred rustfmt churn</title>
<updated>2023-10-11T15:19:46Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-10-11T15:09:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=665ba4f6b6ed2de6f723177d5472e7ee1440599e'/>
<id>urn:sha1:665ba4f6b6ed2de6f723177d5472e7ee1440599e</id>
<content type='text'>
cargo fmt, precisely.
</content>
</entry>
</feed>
