<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-bench/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>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>Bump all crates to 0.1.0</title>
<updated>2022-03-01T13:59:34Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-01T13:59:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e8e9791a9757a32779657c5284b380ae91ca7979'/>
<id>urn:sha1:e8e9791a9757a32779657c5284b380ae91ca7979</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bump minimum tokio to 1.7, since tokio-util now needs that.</title>
<updated>2022-02-25T16:09:24Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-25T15:56:48Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4becaa01b90ea6fc63ef8cef0028326ae56b86fe'/>
<id>urn:sha1:4becaa01b90ea6fc63ef8cef0028326ae56b86fe</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bump anyhow minimal version to 1.0.23</title>
<updated>2022-02-18T17:04:57Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-02-18T17:02:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f9d2ecad275d875165df361f3d873f1111569a89'/>
<id>urn:sha1:f9d2ecad275d875165df361f3d873f1111569a89</id>
<content type='text'>
This is the first one where anyhow::Error impl AsRef&lt;dyn StdError&gt;

We want this because we want to add error reporting functionality
which works with all kinds of errors, which means we need an
anyhow::Error which can be vieweed as a StdError.

(The alternative would be to deref at the call sites of
report_and_exit, making it less ergonomic.)

anyhow 1.0.23 is from November 2019.
</content>
</entry>
<entry>
<title>Upgrade required version of futures crate to 0.3.14</title>
<updated>2022-02-01T14:54:47Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-28T19:50:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c8dd73d55f69c75216ddc69fbca4283e1ae9a595'/>
<id>urn:sha1:c8dd73d55f69c75216ddc69fbca4283e1ae9a595</id>
<content type='text'>
Earlier versions have a bug in UnboundedReceiver that make our new
dirclient tests fail.
</content>
</entry>
<entry>
<title>Bump the patch version of every crate that changed since 0.0.3</title>
<updated>2022-01-31T15:30:52Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-31T15:30:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=01d99373089f8131d1df9758fce45ffaa3fbf659'/>
<id>urn:sha1:01d99373089f8131d1df9758fce45ffaa3fbf659</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Make the native-tls crate optional.</title>
<updated>2022-01-26T19:06:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-26T15:53:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=30b3818a9e31b0ebe96d4a32aa9bceb16610f994'/>
<id>urn:sha1:30b3818a9e31b0ebe96d4a32aa9bceb16610f994</id>
<content type='text'>
This commit puts the native-tls crate behind a feature.  The feature
is off-by-default in the tor-rtcompat crate, but can be enabled
either from arti or arti-client.

There is an included script that I used to test that tor-rtcompat
could build and run its tests with all subsets of its features.

Closes #300
</content>
</entry>
<entry>
<title>arti-bench: add support for multiple samples &amp; averaging</title>
<updated>2022-01-14T15:00:11Z</updated>
<author>
<name>eta</name>
<email>tor@eta.st</email>
</author>
<published>2022-01-13T16:23:11Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=82beb52fca8b973f7889210c6790867ed376eab4'/>
<id>urn:sha1:82beb52fca8b973f7889210c6790867ed376eab4</id>
<content type='text'>
We now do multiple samples (configurable; default 3) per type of
`arti-bench` benchmark run, and take a mean and median average of all
data collected, in order to hopefully be a bit more resilient to random
outliers / variation.

This uses some `futures::stream::Stream` hacks, which might result in
more connections being made than required (and might impact the TTFB
metrics somewhat, at least for downloading).

Results now get collected into a `BenchmarkResults` struct per type of
benchmark, which will be in turn placed into a `BenchmarkSummary` in a
later commit; this will also add the ability to serialize the latter
struct out to disk, for future reference.

part of arti#292
</content>
</entry>
<entry>
<title>Bump all crate versions to 0.0.3.</title>
<updated>2022-01-11T14:40:32Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-11T14:40:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7d3482ca1ae7249b73feeca98595bae5f4c6afe9'/>
<id>urn:sha1:7d3482ca1ae7249b73feeca98595bae5f4c6afe9</id>
<content type='text'>
</content>
</entry>
</feed>
