<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-guardmgr/src, branch arti-v1.1.7</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-07-20T15:42:03Z</updated>
<entry>
<title>tor-guardmgr: bridges: getter for BridgeConfigBuilder.transport</title>
<updated>2023-07-20T15:42:03Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-20T15:34:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3343e70c6822c38d60adb3658af7bb36d3a04337'/>
<id>urn:sha1:3343e70c6822c38d60adb3658af7bb36d3a04337</id>
<content type='text'>
BridgeConfigBuilder is Serialize so this isn't making any new API
promises.  Ideally we'd have getters like this everywhere.
</content>
</entry>
<entry>
<title>Merge branch 'bug638' into 'main'</title>
<updated>2023-07-14T13:35:04Z</updated>
<author>
<name>Alexander Færøy</name>
<email>ahf@torproject.org</email>
</author>
<published>2023-07-14T13:35:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=63a3bbc33cead7cc292ecee15f036a61ecd3b6f0'/>
<id>urn:sha1:63a3bbc33cead7cc292ecee15f036a61ecd3b6f0</id>
<content type='text'>
Stop unconditionally marking bridges as having dir info.

Closes #638

See merge request tpo/core/arti!1408</content>
</entry>
<entry>
<title>Bridges: deduplicate addresses.</title>
<updated>2023-07-13T20:58:12Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-13T20:58:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b8334292fb11494f8a9bf768a8c5b606ef3ce79f'/>
<id>urn:sha1:b8334292fb11494f8a9bf768a8c5b606ef3ce79f</id>
<content type='text'>
Currently we list an address for a bridge twice if it is listed both
in the bridge line and the bridge descriptor. That can't be right.
</content>
</entry>
<entry>
<title>Better report for any recurrence of bug #638.</title>
<updated>2023-07-13T19:43:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-13T19:42:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3f2d4f8cec2c349ab38f7e4a006f3396318027ce'/>
<id>urn:sha1:3f2d4f8cec2c349ab38f7e4a006f3396318027ce</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Stop unconditionally marking bridges as having dir info.</title>
<updated>2023-07-13T19:43:42Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-13T19:28:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7a915f5454599ee0042fe243a82a78510501c76f'/>
<id>urn:sha1:7a915f5454599ee0042fe243a82a78510501c76f</id>
<content type='text'>
When we implemented bridges, we added code in 08473872abccf389 to
conditionally mark their directory info as present or not present.
But the we didn't remove the old code to mark them present
unconditionally!

Fixes #638.
</content>
</entry>
<entry>
<title>Merge branch 'clippy-allow' into 'main'</title>
<updated>2023-07-11T09:37:42Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2023-07-11T09:37:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3acc2af4f3411588f80669ae1980679dd260b119'/>
<id>urn:sha1:3acc2af4f3411588f80669ae1980679dd260b119</id>
<content type='text'>
clippy: Allow some of our existing code patterns

See merge request tpo/core/arti!1396</content>
</entry>
<entry>
<title>rng ranges: Use gen_range_infallible() for Duration::ZERO..=T</title>
<updated>2023-07-10T15:08:03Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-07T13:19:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b151237a7f8651ed8694748832af05786a7eccfd'/>
<id>urn:sha1:b151237a7f8651ed8694748832af05786a7eccfd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Run maint/add_warning to actually apply new lint allows</title>
<updated>2023-07-10T12:49:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-10T11:19:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=473447a82e099fd52a674c28f5bc24b3e05208c0'/>
<id>urn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove some needless into_iter() calls.</title>
<updated>2023-07-10T11:33:21Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-07T18:06:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=22f55b7cf896f4aced1daf61eda795df4df738b2'/>
<id>urn:sha1:22f55b7cf896f4aced1daf61eda795df4df738b2</id>
<content type='text'>
Clippy nightly now detects when you're calling into_iter() and
passing the result into something that accepts an
`impl IntoIterator`.
</content>
</entry>
<entry>
<title>rng ranges: Use inclusive Duration ranges in several places</title>
<updated>2023-07-07T15:13:52Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-07T13:10:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bcc3e6fef8b863fa6a863aae2d6234fba7fb99f6'/>
<id>urn:sha1:bcc3e6fef8b863fa6a863aae2d6234fba7fb99f6</id>
<content type='text'>
Many of these call sites would panic if, somehow, the upper bound was
zero.  In most cases it is very complicated to see if whether this
could happen.

However, there is a better answer:

Durations are (conceptually) dense, so picking the closed set (which
includes its boundary) rather than the open one (which doesn't) will
make little practical difference.

So change four call sites to use `..=` instead of just `..`.
</content>
</entry>
</feed>
