<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-proto, branch arti-v1.1.7</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-08-01T14:57:55Z</updated>
<entry>
<title>Increment patchlevel versions of crates with minor changes</title>
<updated>2023-08-01T14:57:55Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-01T14:57:55Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3acdf102c705314aec63679e97240bb7d981d1c8'/>
<id>urn:sha1:3acdf102c705314aec63679e97240bb7d981d1c8</id>
<content type='text'>
These crates are at version 0.x.y, so we don't need to distinguish
new-feature changes from other changes:

```
tor-basic-utils
fs-mistrust
tor-error
tor-geoip
tor-checkable
tor-linkspec
tor-netdoc
tor-netdir
tor-persist
tor-ptmgr
tor-hsservice
```

This crate has a breaking change, but only when the semver-breaking
feature `experimental-api` is enabled:

```
tor-config
```

This crate is at version 1.x.y, but has no new public APIs, and
therefore does not need a minor version bump:

```
arti
```
</content>
</entry>
<entry>
<title>Update minor versions on crates that have had breaking changes</title>
<updated>2023-08-01T14:51:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-01T14:51:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6f2ae5960393b64c1d7615d2d523e050d3bebe5a'/>
<id>urn:sha1:6f2ae5960393b64c1d7615d2d523e050d3bebe5a</id>
<content type='text'>
These crates had first-order breaking changes:

```
retry-error
tor-keymgr
tor-proto
tor-hsclient
tor-rtmock
```

Additionally, these broke because they re-exposed RetryError:

```
tor-circmgr
```

Additionally, these broke because they may re-expose something from
tor-proto:

```
    arti-client
    tor-chanmgr
    tor-dirclient
    tor-dirmgr
    tor-guardmgr
```

Additionally, these broke for other fiddly reasons:

`tor-ptmgr` implements traits from tor-chanmgr, which has a breaking
change above.

`arti-hyper` exposes types from arti-client in its API.
</content>
</entry>
<entry>
<title>tor-proto: Rename create_firsthop() to wait_for_create().</title>
<updated>2023-07-27T09:56:18Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-07-27T09:56:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ecfec3b8275e5c13d8cb2fda44b0fb2ecacb8b98'/>
<id>urn:sha1:ecfec3b8275e5c13d8cb2fda44b0fb2ecacb8b98</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-proto: Update handle_control docs.</title>
<updated>2023-07-26T18:36:54Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-07-26T18:25:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6f22c16eccdc3f68bd25f45cde08684f647115c3'/>
<id>urn:sha1:6f22c16eccdc3f68bd25f45cde08684f647115c3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-proto: Add functions for handling Shutdown and AddFakeHop messages.</title>
<updated>2023-07-26T18:36:50Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-07-26T18:00:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=331ec1033af14b048e1b29e7f8d5a3593c748535'/>
<id>urn:sha1:331ec1033af14b048e1b29e7f8d5a3593c748535</id>
<content type='text'>
This helps reduce code duplication, as `CtrlMsg::Shutdown` and
`CtrlMsg::AddFakeHop` are now handled in multiple places.
</content>
</entry>
<entry>
<title>tor-proto: Extract first-hop creation to a separate function.</title>
<updated>2023-07-26T18:36:47Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-07-26T17:03:51Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fee4baa17f8dbf7a177147b81ee667b5117aed22'/>
<id>urn:sha1:fee4baa17f8dbf7a177147b81ee667b5117aed22</id>
<content type='text'>
I think it's safe to handle `ChanMsg::Create` separately, because
there's nothing for the reactor to do until the first hop of the circuit
is created (so blocking on this _should_ be alright).
</content>
</entry>
<entry>
<title>tor-proto: Create a function for handling the initial CREATE cell.</title>
<updated>2023-07-26T18:35:04Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2023-07-26T16:41:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=98b9be0f2d3e25eba7537bd115bd93682b93399b'/>
<id>urn:sha1:98b9be0f2d3e25eba7537bd115bd93682b93399b</id>
<content type='text'>
This logic from `create_firsthop()` was extracted (copied) from
`Reactor::run_once()`. A future commit will update `Reactor::run_once()`
to use `create_firsthop()`.
</content>
</entry>
<entry>
<title>tor-circmgr: Add two possibly-needed docsrs annotations</title>
<updated>2023-07-12T14:32:26Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-12T14:28:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f6d5cae574db663af9ced755c938b56c58c37748'/>
<id>urn:sha1:f6d5cae574db663af9ced755c938b56c58c37748</id>
<content type='text'>
I don't know if these are needed because the rules are not documented
afaict.  But it seems like probably they ought to be there?
</content>
</entry>
<entry>
<title>tor-proto: Conversation: drop two otiose cfg(feature)</title>
<updated>2023-07-12T14:31:30Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-12T14:20:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=1fa692d63d42ca4f5e26d115b55c24e1ef64f84c'/>
<id>urn:sha1:1fa692d63d42ca4f5e26d115b55c24e1ef64f84c</id>
<content type='text'>
These fns are in a feature-gated impls on feature-gated structs.
</content>
</entry>
<entry>
<title>Merge branch 'clippy-allow' into 'main'</title>
<updated>2023-07-11T09:37:42Z</updated>
<author>
<name>Ian Jackson</name>
<email>iwj@torproject.org</email>
</author>
<published>2023-07-11T09:37:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3acc2af4f3411588f80669ae1980679dd260b119'/>
<id>urn:sha1:3acc2af4f3411588f80669ae1980679dd260b119</id>
<content type='text'>
clippy: Allow some of our existing code patterns

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