<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-basic-utils, branch arti-v1.0.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.0.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.0.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-09-01T12:59:49Z</updated>
<entry>
<title>Bump crate versions in preparation for Arti 1.0.0 release.</title>
<updated>2022-09-01T12:59:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-09-01T12:52:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=96875ea20875e3a5cfc9f348365f19a158578190'/>
<id>urn:sha1:96875ea20875e3a5cfc9f348365f19a158578190</id>
<content type='text'>
Because we want to work more on ensuring that our semver stability
story is solid, we are _not_ bumping arti-client to 1.0.0 right now.

Here are the bumps we _are_ doing.  Crates with "minor" bumps have
had API breaks; crates with "patch" bumps have had new APIs added.

Note that `tor-congestion` is not bumped here: it's a new crate, and
hasn't been published before.

```
tor-basic-utils         minor
fs-mistrust             minor
tor-config              minor
tor-rtcompat            minor
tor-rtmock              minor
tor-llcrypto            patch
tor-bytes               patch
tor-linkspec            minor
tor-cell                minor
tor-proto               minor
tor-netdoc              patch
tor-netdir              minor
tor-persist             patch
tor-chanmgr             minor
tor-guardmgr            minor
tor-circmgr             minor
tor-dirmgr              minor
arti-client             minor
arti-hyper              minor
arti                    major
arti-bench              minor
arti-testing            minor
```
</content>
</entry>
<entry>
<title>tor-basic-utils: Provide IoErrorExt is_not_a_directory()</title>
<updated>2022-08-25T14:58:29Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-08-18T14:16:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2fa75be6606301d59ef5c48f5b7abdaefefd620e'/>
<id>urn:sha1:2fa75be6606301d59ef5c48f5b7abdaefefd620e</id>
<content type='text'>
We're going to want this functionality, which isn't in the stable
stdlib.
</content>
</entry>
<entry>
<title>enable doc_auto_cfg feature on every crate when documenting for docs.rs</title>
<updated>2022-08-24T16:22:41Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2022-08-17T19:13:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7f939fa4804b3c934343141b79e8e2ded5fe0b0d'/>
<id>urn:sha1:7f939fa4804b3c934343141b79e8e2ded5fe0b0d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bump patch versions on crates that have new APIs.</title>
<updated>2022-08-01T13:56:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-08-01T13:56:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=859ae4acd00dc63ee3d903b21eb34f9267377185'/>
<id>urn:sha1:859ae4acd00dc63ee3d903b21eb34f9267377185</id>
<content type='text'>
Do _not_ bump the dependency versions on crates that have had no
changes since arti 0.0.5, since those crates do not depend on the
new APIs.

```
cargo set-version -p tor-basic-utils   --bump patch
cargo set-version -p tor-llcrypto      --bump patch
git restore crates/tor-checkable
git restore crates/tor-consdiff
git restore crates/tor-rtmock
```
</content>
</entry>
<entry>
<title>tor-basic-utils: Add a test for DropNotifyWatchSender</title>
<updated>2022-07-19T18:04:34Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-07-19T18:04:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=44402f722e27e3c9e3f616e1d84de4fa35aa8ad4'/>
<id>urn:sha1:44402f722e27e3c9e3f616e1d84de4fa35aa8ad4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-basic-utils: Add ref to upstream issue re drop</title>
<updated>2022-07-19T18:00:23Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-07-19T18:00:23Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c7933de0ab32ad9782c87c6247057b4c51cd053b'/>
<id>urn:sha1:c7933de0ab32ad9782c87c6247057b4c51cd053b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-basic-utils: Add comment about lack of race</title>
<updated>2022-07-19T16:21:22Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-07-19T16:21:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bd41e29f3332adca562c3dacb20e050bbf9d9c4f'/>
<id>urn:sha1:bd41e29f3332adca562c3dacb20e050bbf9d9c4f</id>
<content type='text'>
In answer to
  https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/632#note_2822107

I think this is subtle enough that it deserves a comment.
</content>
</entry>
<entry>
<title>arti-client: Provide DropNotifyWatchSender</title>
<updated>2022-07-18T17:13:13Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-07-18T16:21:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bc498bc7a082d54a4ee28f3353fd0fc9dac4d46c'/>
<id>urn:sha1:bc498bc7a082d54a4ee28f3353fd0fc9dac4d46c</id>
<content type='text'>
There are going to be some tasks (well, right away, one task) which
will want to go away when the sender is dropped.

The docs in postage are silent, but postage::watch::Sender does not
have a Drop impl so I don't think we can rely on the Receivers getting
None from their Stream impl.

So we're going to have the watch send Options, which are None only
when the sender is dropped.
</content>
</entry>
<entry>
<title>Provide maybe_send on postage::watch::Sender, via extension trait</title>
<updated>2022-07-18T17:13:13Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-07-18T11:04:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7acdd217507c1020e52d2146a013d0fe4e8f964e'/>
<id>urn:sha1:7acdd217507c1020e52d2146a013d0fe4e8f964e</id>
<content type='text'>
We need to replace the AtomicBool for dormant mode with something that
can wake up tasks.  postage::watch is the right shape.

But we want to be able to update it but suppress no-op updates.
(There is going to be a call site where no-op updates can occur.)

In the absence of a suitable upstream method as requested here
  https://github.com/austinjones/postage-rs/issues/56
we introduce this facility via an extension trait.
</content>
</entry>
<entry>
<title>Merge branch 'cirmgr_error_cleanup' into 'main'</title>
<updated>2022-07-15T15:58:44Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2022-07-15T15:58:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=44f37b2d073ec38aef2c216eca57722ef2a43507'/>
<id>urn:sha1:44f37b2d073ec38aef2c216eca57722ef2a43507</id>
<content type='text'>
Clean-ups in circmgr errors

See merge request tpo/core/arti!625</content>
</entry>
</feed>
