<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-guardmgr/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>Use derive_more to derive AsRef.</title>
<updated>2022-03-30T14:41:40Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-29T19:16:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=df3c51c8a0429b22b0ea62dbb356aff3f97de257'/>
<id>urn:sha1:df3c51c8a0429b22b0ea62dbb356aff3f97de257</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Reformat tor-guardmgr/Cargo.toml.</title>
<updated>2022-03-30T14:41:40Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-03-29T19:13:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5233d35223230db1c62e9a71bdb2bdcd9dcb8c86'/>
<id>urn:sha1:5233d35223230db1c62e9a71bdb2bdcd9dcb8c86</id>
<content type='text'>
</content>
</entry>
<entry>
<title>derive_builder: Switch to upstream 0.11</title>
<updated>2022-03-16T16:34:44Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-03-16T14:52:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=da787d074a04c97a1e28709f53f1cff5127b7ac9'/>
<id>urn:sha1:da787d074a04c97a1e28709f53f1cff5127b7ac9</id>
<content type='text'>
This has the different syntax for builder field attributes than what I
originally proposed in my MR, and which therefore is in the pinned
branch.

My upstream MR for the field attributes feature was morged:
  https://github.com/colin-kiegel/rust-derive-builder/issues/239
</content>
</entry>
<entry>
<title>humantime: Update to humantime-serde 1.1.1</title>
<updated>2022-03-14T10:33:59Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-03-11T17:24:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8b8c2a426e37b1c543a2e0ae7d01f01d61fa7170'/>
<id>urn:sha1:8b8c2a426e37b1c543a2e0ae7d01f01d61fa7170</id>
<content type='text'>
This has the humantime_serde::option module, which we have upstreamed
and are about to switch to.

The remaining dependency with  version = "1"  is going to be removed
in a moment.
</content>
</entry>
<entry>
<title>Use git source for derive_builder for now, for attrs feature</title>
<updated>2022-03-07T15:56:57Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-03-04T15:09:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=416b56d852a74ff8f8a2e6f1794c8390f9b08afe'/>
<id>urn:sha1:416b56d852a74ff8f8a2e6f1794c8390f9b08afe</id>
<content type='text'>
We are going to want to specify custom attributes on fields of the
builder struct.  This feature was missing from derive_builder.

This commitid is the current head of my MR branch
  https://github.com/colin-kiegel/rust-derive-builder/pull/237
  https://github.com/ijackson/rust-derive-builder/tree/builder-field-attrs
Using the commitid prevents surprises if that branch is updated.

We will require this newer version of derive_builder.  The version
will need to be bumped again later, assuming the upstream MR is merged
and upstream do a release containing the needed changes.
</content>
</entry>
<entry>
<title>Move skip_fmt into tor-basic-utils</title>
<updated>2022-03-04T11:45:24Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-03-04T11:42:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ebfd7349565f0f354906a78ad2ce8f8d2b88bd35'/>
<id>urn:sha1:ebfd7349565f0f354906a78ad2ce8f8d2b88bd35</id>
<content type='text'>
Code motion and the minimal mechanical changes.

As per
  https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/375#note_2783078
</content>
</entry>
<entry>
<title>Replace manual Debug impl with educe in tor-guardmgr</title>
<updated>2022-03-02T18:03:00Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-03-02T14:47:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b2d8c14c905a32fad684cb5389bfc35e5cd8a924'/>
<id>urn:sha1:b2d8c14c905a32fad684cb5389bfc35e5cd8a924</id>
<content type='text'>
</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>Make coarsetime dependency and traffic-timestamping non-optional.</title>
<updated>2022-02-25T15:31:01Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-25T15:31:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3d7d609922586e5824420dcb9d0017440cba66d4'/>
<id>urn:sha1:3d7d609922586e5824420dcb9d0017440cba66d4</id>
<content type='text'>
Previously coarsetime and the traffic-timestamp feature were
enabled, since they were only required for a small corner of the
guardmgr algorithm.

But in 1.0 and beyond we'll be adding a bunch of other features (eg,
netflow padding, DoS prevention) that will need coarsetime all over
the place.

And since we're going to be doing coarsetime all over the place, the
previous justification for making traffic-timestamping optional (the
tiny performance hit) is no longer relevant.
</content>
</entry>
</feed>
