<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates, branch arti-v0.2.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.2.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.2.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-04-01T13:15:18Z</updated>
<entry>
<title>Bump all arti*, tor* crates to 0.2.0</title>
<updated>2022-04-01T13:15:18Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-01T13:15:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5b2fc118df0524144e6b2c34fdcce3d0fb692d24'/>
<id>urn:sha1:5b2fc118df0524144e6b2c34fdcce3d0fb692d24</id>
<content type='text'>
Not all of these strictly need to be bumped to 0.2.0; many could go
to 0.1.1 instead.  But since everything at the tor-rtcompat and
higher layers has had breaking API changes, it seems not so useful
to distinguish.  (It seems unlikely that anybody at this stage is
depending on e.g. tor-protover but not arti-client.)
</content>
</entry>
<entry>
<title>Bump caret, retry-error to 0.1.1</title>
<updated>2022-04-01T13:14:46Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-01T13:05:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=aae242af22934275bf8852e35da3d56de44373bb'/>
<id>urn:sha1:aae242af22934275bf8852e35da3d56de44373bb</id>
<content type='text'>
Unlike the rest of the crates, these don't have a "tor-" or "arti-"
prefix, and are potentially used by code outside arti.  With that in
mind, it's probably for the best not to bump them to 0.2.0 along
with the rest of our crates.

They have had no changes since 0.1.0 other than refactoring and
changing of clippy lints.  Therefore, I'm not bumping the
dependencies from other crates onto these: it's fine whether our
other crates use caret/retry-error 0.1.0 or 0.1.1.
</content>
</entry>
<entry>
<title>Merge branch 'upgrade_pre_020' into 'main'</title>
<updated>2022-04-01T12:48:50Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-01T12:48:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ae387f5eebbe85ce01e33f6350bc48c59d5495b7'/>
<id>urn:sha1:ae387f5eebbe85ce01e33f6350bc48c59d5495b7</id>
<content type='text'>
Run cargo upgrade/update in preparation for 0.2.0

See merge request tpo/core/arti!444</content>
</entry>
<entry>
<title>Upgrade async-broadcast =&gt; 0.4.0</title>
<updated>2022-04-01T12:10:38Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-01T12:10:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=95237e63ce955af498eab71a01822f38e3004d20'/>
<id>urn:sha1:95237e63ce955af498eab71a01822f38e3004d20</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Upgrade rlimit -&gt; 0.8.0</title>
<updated>2022-04-01T12:03:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-01T12:03:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9190dfea77487bc4e669c4b12d1bd3b1735d2ba1'/>
<id>urn:sha1:9190dfea77487bc4e669c4b12d1bd3b1735d2ba1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'dir-munger-v2' into 'main'</title>
<updated>2022-03-31T15:43:28Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-31T15:43:28Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=259622bc3a1ea907c0782c8f833e37415ed51173'/>
<id>urn:sha1:259622bc3a1ea907c0782c8f833e37415ed51173</id>
<content type='text'>
Implement a directory munger to simulate pathological cases in arti-testing (v2)

Closes #397

See merge request tpo/core/arti!442</content>
</entry>
<entry>
<title>Re-order attributes so that we can build with Rust 1.53.</title>
<updated>2022-03-31T15:11:02Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-31T15:06:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0725e388a592a8ab7e2235fef2b2d7a396fe64d0'/>
<id>urn:sha1:0725e388a592a8ab7e2235fef2b2d7a396fe64d0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Typo fix.</title>
<updated>2022-03-31T14:34:11Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2022-03-31T14:34:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=68b614ade1a92e10cc81a3bb7b7a19a15fd48dde'/>
<id>urn:sha1:68b614ade1a92e10cc81a3bb7b7a19a15fd48dde</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Directory filtering in arti-testing.</title>
<updated>2022-03-31T13:27:27Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-30T12:48:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e98aa50e72f5ee15d676c0fec267621d26fbe94a'/>
<id>urn:sha1:e98aa50e72f5ee15d676c0fec267621d26fbe94a</id>
<content type='text'>
This feature allows us to detect different failing cases for
arti#329 that would otherwise be hard to induce.  It works by
filtering consensus directory objects and/or microdescriptor objects
before introducing them to the directory manager.

Closes #397.
</content>
</entry>
<entry>
<title>tor-netdoc: Conditionally expose document fields.</title>
<updated>2022-03-31T13:27:27Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-31T13:20:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b1b7ef00a0f96c3d878788cd890ed67656bcc1f4'/>
<id>urn:sha1:b1b7ef00a0f96c3d878788cd890ed67656bcc1f4</id>
<content type='text'>
This commit uses the `visibility` and `visible` crates to
conditionally make certain structs and their fields public
(respectively).  This is incredibly dangerous to use for anything
besides testing, and I've tried to write the documentation for the
feature accordingly.
</content>
</entry>
</feed>
