<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-testing/Cargo.toml, 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>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 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>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>Move ArtiConfig to new arti::cfg module</title>
<updated>2022-03-21T11:42:33Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-03-21T10:23:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8aea5c9e43a823a16d170356b69148d085a06745'/>
<id>urn:sha1:8aea5c9e43a823a16d170356b69148d085a06745</id>
<content type='text'>
Code motion and import fixups.
</content>
</entry>
<entry>
<title>arti-testing: Initial support for broken TCP.</title>
<updated>2022-03-07T15:12:48Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-04T22:43:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ca6070b962d50ba114b6cfdcc0dc72b0e5b228e3'/>
<id>urn:sha1:ca6070b962d50ba114b6cfdcc0dc72b0e5b228e3</id>
<content type='text'>
This commit adds support for a BrokenTcp provider that can make
connection attempts fail or time out.  It doesn't yet have a way to
turn on the failure.
</content>
</entry>
<entry>
<title>arti-testing: Initial implementation</title>
<updated>2022-03-03T18:05:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-02T15:03:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9329c7b878eadba0344802632b97f23524c9d8f3'/>
<id>urn:sha1:9329c7b878eadba0344802632b97f23524c9d8f3</id>
<content type='text'>
This commit adds a new program to try to implement the ideas behind
experimentation in arti#329.  In particular, it tries to implement
basic client "can I bootstrap and connect" functionality testing,
with a lot of instrumentation, and support for breaking things.

So far, the instrumentation is limited to counting TCP bytes and
connections, and counting events.  Still, this is enough to measure
behavior on some of the incorrect-clock tests.

NOTE:

For now, you are _required_ to pass in an explicit configuration, in
hopes that this will lead you to override your storage directories
for doing specific experiments.
</content>
</entry>
</feed>
