<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-guardmgr/src, branch arti-v0.5.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.5.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.5.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-06-24T13:23:38Z</updated>
<entry>
<title>clippy: Consolidate many lints in maint/add_warning</title>
<updated>2022-06-24T13:23:38Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-24T12:24:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=23c352b96bf07c981bb396fa34ce83e512ada0b2'/>
<id>urn:sha1:23c352b96bf07c981bb396fa34ce83e512ada0b2</id>
<content type='text'>
Found these by disabling the nightly dbg macro special case.  Now, we
have a mechanism for globally adding suppressions to tests, we can use
that instead.
</content>
</entry>
<entry>
<title>Run maint/add_warning crates/*/src/{lib,main}.rs</title>
<updated>2022-06-23T18:15:42Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-23T18:15:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=589c6e52bb49ccfe6c0ad9d18d6b994978e46c6c'/>
<id>urn:sha1:589c6e52bb49ccfe6c0ad9d18d6b994978e46c6c</id>
<content type='text'>
Update all lint blocks
</content>
</entry>
<entry>
<title>Merge branch 'reachable_addrs_v2' into 'main'</title>
<updated>2022-06-17T13:16:16Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-17T13:16:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9ae57e8bc477229935adae6b2e81846cee03cd17'/>
<id>urn:sha1:9ae57e8bc477229935adae6b2e81846cee03cd17</id>
<content type='text'>
Implement support for reachable_addrs

Closes #491 and #93

See merge request tpo/core/arti!583</content>
</entry>
<entry>
<title>Rename guardset-selection function.</title>
<updated>2022-06-17T12:47:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-15T19:14:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f4c9b9cc1e5c726c01d3c956ac1fa9f7bc7b98a7'/>
<id>urn:sha1:f4c9b9cc1e5c726c01d3c956ac1fa9f7bc7b98a7</id>
<content type='text'>
Also, improve its documentation.
</content>
</entry>
<entry>
<title>Rename pick_guard, pick_guard_ext.</title>
<updated>2022-06-17T12:47:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-15T19:07:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=03568cd4a5643be5314dd43b029596f276e99f41'/>
<id>urn:sha1:03568cd4a5643be5314dd43b029596f276e99f41</id>
<content type='text'>
Now the primary exposed function is `pick_guard` again.

This commit is just function renaming.
</content>
</entry>
<entry>
<title>Refactor and document issues with modify_hop.</title>
<updated>2022-06-17T12:47:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-15T19:03:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1be44891c9d9a7d30ade2178ecd04fad08cc8026'/>
<id>urn:sha1:1be44891c9d9a7d30ade2178ecd04fad08cc8026</id>
<content type='text'>
At the site of modify_hop, we now have a comment explaining the
internal-error issue.

To make the internal error less likely, we lower the modify_hop call
in lib.rs into GuardSet, where it can make sure it's looking at the
same filter as was used to select the guard.

The function name "pick_guard_ext" is not permanent; I'm going to
rename it in the next commit.
</content>
</entry>
<entry>
<title>API-fix for extend_sample_as_needed.</title>
<updated>2022-06-17T12:47:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-10T14:07:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=96dfa97473450d6e4cbd93b0ffa8a11021096298'/>
<id>urn:sha1:96dfa97473450d6e4cbd93b0ffa8a11021096298</id>
<content type='text'>
Previously, the API said "you need to call this in a loop till it
returns false".  We did that in one place, but not another.

With the introduction of filters, forgetting to loop here becomes a
bug: so instead, change the behavior of extend_sample_as_needed so
it handles looping itself.
</content>
</entry>
<entry>
<title>Remove some outdated comments.</title>
<updated>2022-06-17T12:47:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-10T13:55:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a92dfa0b2aab07ba6cffd9d9be916f9096a6b33f'/>
<id>urn:sha1:a92dfa0b2aab07ba6cffd9d9be916f9096a6b33f</id>
<content type='text'>
These all say, in one form or another, "there is no guard filtering;
there is only one selection".  That's now false.
</content>
</entry>
<entry>
<title>Tweak parameters in guardmgr tests to improve testnet behavior.</title>
<updated>2022-06-17T12:47:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-10T13:37:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=89f9e1decb7872d688d126fe41ab28b6bd0504a0'/>
<id>urn:sha1:89f9e1decb7872d688d126fe41ab28b6bd0504a0</id>
<content type='text'>
The fake network we construct for these tests is small in ways that
can sometimes cause weird behavior with guard filters.  We fix this
by adjusting the parameters of the guard selection algorithm
accordingly in the tests.

With these new parameters, #491 no longer occurs.

This commit also adds comments to explain why the parameters are set
as they are.

Closes #491.
</content>
</entry>
<entry>
<title>GuardMgr: Support for multiple guard sets</title>
<updated>2022-06-17T12:47:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-01T17:50:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=48a86506be0e9bb1dc3cab0ba3c05a9fda6f1e46'/>
<id>urn:sha1:48a86506be0e9bb1dc3cab0ba3c05a9fda6f1e46</id>
<content type='text'>
guard-spec.txt specifies that we have multiple separate samples of
guards that we can use depending on whether the filter is
restrictive or not.  Here we implement the rules for switching
between samples.
</content>
</entry>
</feed>
