<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dircommon/src/config.rs, 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-07-23T10:13:34Z</updated>
<entry>
<title>tor-checkable: TimeRangeBound: Rename extend_tolerance to extend_end_bound</title>
<updated>2026-07-23T10:13:34Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-07-20T14:28:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7ce9f5c34c3bdb95e87dac5c8348f6937256c5f5'/>
<id>urn:sha1:7ce9f5c34c3bdb95e87dac5c8348f6937256c5f5</id>
<content type='text'>
It was confusing that one of these functions had "which bound"
mentioned in its name, but the other didn't.  So add `end` and switch
from `tolerance` to `bound` (see previous commit message).

*This* commit should deal only in `extend_tolerance` and `end` and
shouldn't touch `extend_start_bound` or `extend_pre_tolerance`.
</content>
</entry>
<entry>
<title>tor-checkable: TimeRangeBound: Rename extend_pre_tolerance to extend_start_bound</title>
<updated>2026-07-23T10:13:34Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-07-20T10:09:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=306fffc11215201aa1b5d6baf84f985bb3fee1bf'/>
<id>urn:sha1:306fffc11215201aa1b5d6baf84f985bb3fee1bf</id>
<content type='text'>
Although it is often used to apply a tolerance, it doesn't make sense
to say that this is extending the "tolerance" of a `TimeRangeBound`.
A `TimeRangeBound` doesn't have a tolerance, only bounds.

Also we should be consistent in our terminology, and use `start`
rather than `pre`.

We'll rename the other method too.  Doing them one at a time will
makes it easier to spot any "pre/start" vs "&lt;nothing&gt;/end" slips:
*this* commit should deal only in `pre` and `start` and shouldn't
touch `extend_tolerance`.
</content>
</entry>
<entry>
<title>Use new TimeRangeBound name throughout the tree</title>
<updated>2026-07-16T15:47:50Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-07-16T14:35:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=92c26c4c07be73c91890ed3d7d4e53a06f26d0a1'/>
<id>urn:sha1:92c26c4c07be73c91890ed3d7d4e53a06f26d0a1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>maint: Run maint/add_warning to deny string slices</title>
<updated>2026-06-09T15:36:01Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-06-09T15:36:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9f5752a77fb57052c06ead0eeae606831f1e8e97'/>
<id>urn:sha1:9f5752a77fb57052c06ead0eeae606831f1e8e97</id>
<content type='text'>
This commit executes maint/add_warning with the just added change to
deny string slices except in tests.

I recommend auditing this by checking out the previous commit followed
by running the script yourself and then verifying that the diff is
identical to this commit.

This commit makes cargo clippy fail.  We will add exceptions in the next
commit.
</content>
</entry>
<entry>
<title>dircommon: Port to use derive_deftly(TorConfig)</title>
<updated>2026-02-17T13:49:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-02-11T19:32:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7fffa9453732decc8b970d94add5529d39472a9d'/>
<id>urn:sha1:7fffa9453732decc8b970d94add5529d39472a9d</id>
<content type='text'>
Some of the behaviors of the existing types here are nonstandard;
I've kept them and documented them, to avoid breaking compatibility.
</content>
</entry>
<entry>
<title>tor-dircommon: De-duplicate example from AuthorityContact</title>
<updated>2026-01-22T15:12:05Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-01-20T09:38:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ff59df5de9b4c9191561127975a70009e6d26ac8'/>
<id>urn:sha1:ff59df5de9b4c9191561127975a70009e6d26ac8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-dircommon: Fix clippy warning</title>
<updated>2026-01-22T15:11:59Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-01-19T09:52:10Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3370dffe8705028033a70e3418c135373eb8a604'/>
<id>urn:sha1:3370dffe8705028033a70e3418c135373eb8a604</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-dircommon: Remove legacy authority syntax</title>
<updated>2026-01-22T15:11:59Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-01-19T09:00:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bdc241085ab4b4656168a192fef9c033d55f4a55'/>
<id>urn:sha1:bdc241085ab4b4656168a192fef9c033d55f4a55</id>
<content type='text'>
Because arti 2.0 is pending, it is good to get rid of technical debt,
such as the legacy syntax for specifying directory authorities, which
had been replaced by prop330 a few months ago.
</content>
</entry>
<entry>
<title>tor-dircommon: Document prop330 syntax better</title>
<updated>2026-01-22T15:11:59Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-01-19T08:59:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ffe151552c373b3628f9ecae8de7ea1861cb0a13'/>
<id>urn:sha1:ffe151552c373b3628f9ecae8de7ea1861cb0a13</id>
<content type='text'>
This commit adds more documentation/examples for the prop330 syntax for
specifying directory authorities.
</content>
</entry>
<entry>
<title>Fix name of clippy lint to unchecked_time_subtraction (2)</title>
<updated>2025-11-06T11:28:22Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2025-11-06T11:23:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a5fd5c48ea059a80cc1f6c50e248654b5ff3aaff'/>
<id>urn:sha1:a5fd5c48ea059a80cc1f6c50e248654b5ff3aaff</id>
<content type='text'>
Run maint/add_warning
</content>
</entry>
</feed>
