<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-proto/src/channel/reactor.rs, branch arti-v1.1.1</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.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-12-12T16:40:51Z</updated>
<entry>
<title>tor-proto: reactor tests: Use debug fmt on an error</title>
<updated>2022-12-12T16:40:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-12-12T15:36:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8fea4dd6d32dc5e41698ebc06d2466b0ce5845c6'/>
<id>urn:sha1:8fea4dd6d32dc5e41698ebc06d2466b0ce5845c6</id>
<content type='text'>
In tests, debug fmt is usually appropriate.

Found while looking for a candidate for
  https://gitlab.torproject.org/tpo/core/arti/-/issues/680
</content>
</entry>
<entry>
<title>tor-linkspec: Remove the old OwnedFoo::new() functions</title>
<updated>2022-10-06T19:13:05Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-05T18:08:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=299ebd729d697cde69dc720e358abf933af2a054'/>
<id>urn:sha1:299ebd729d697cde69dc720e358abf933af2a054</id>
<content type='text'>
These are now builders.
</content>
</entry>
<entry>
<title>add feature annotation not added by doc_auto_cfg</title>
<updated>2022-08-24T16:22:41Z</updated>
<author>
<name>trinity-1686a</name>
<email>trinity@deuxfleurs.fr</email>
</author>
<published>2022-08-18T00:04:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=426a59b2ba591e20a13c568d665310c55e2f8e53'/>
<id>urn:sha1:426a59b2ba591e20a13c568d665310c55e2f8e53</id>
<content type='text'>
</content>
</entry>
<entry>
<title>channel padding: Only do anything with link protocol 5</title>
<updated>2022-08-17T09:54:41Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-08-16T17:56:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d4ce701fa4882c3c56a7b400e983807a0adff0da'/>
<id>urn:sha1:d4ce701fa4882c3c56a7b400e983807a0adff0da</id>
<content type='text'>
Or rather, if we *didn't* negotiate 4, which is too old.

As per
  https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/657#note_2828354
</content>
</entry>
<entry>
<title>channel reactor: Add some commented-out debug for padding</title>
<updated>2022-08-17T09:54:41Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-08-09T11:35:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4111c63bd4606b1d23ecd276f706edcc22a4f822'/>
<id>urn:sha1:4111c63bd4606b1d23ecd276f706edcc22a4f822</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rename ChannelsParams types to ChannelPaddingInstructions</title>
<updated>2022-08-17T09:54:41Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-08-09T09:49:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=94dd3361e24335c187bbf4d3a3ec0971b186da3c'/>
<id>urn:sha1:94dd3361e24335c187bbf4d3a3ec0971b186da3c</id>
<content type='text'>
As per
  https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/657#note_2826167

This makes some lines too long; I will run rustfmt in a separate
commit for clarity.
</content>
</entry>
<entry>
<title>tor-proto channel padding: Document PADDING_NEGOTIATE overwriting</title>
<updated>2022-08-17T09:54:41Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-08-08T14:33:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=481bf0bbe926246e7017584b8b5cba310054f8aa'/>
<id>urn:sha1:481bf0bbe926246e7017584b8b5cba310054f8aa</id>
<content type='text'>
As per
  https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/657#note_2825979
</content>
</entry>
<entry>
<title>tor-proto: Make "testing" feature that exports some things</title>
<updated>2022-08-16T17:43:23Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-07-22T16:38:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=db3fafb0d4f4a9abf0dfd7ec11fd1cce15f01815'/>
<id>urn:sha1:db3fafb0d4f4a9abf0dfd7ec11fd1cce15f01815</id>
<content type='text'>
We are going to want this for through-the-layers padding control
testing.
</content>
</entry>
<entry>
<title>channel padding: Send negotiation cells</title>
<updated>2022-08-16T17:43:23Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-08-02T11:48:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=50ca64218e2a9f3b79bed4dc5dc19dfe6abb62e5'/>
<id>urn:sha1:50ca64218e2a9f3b79bed4dc5dc19dfe6abb62e5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-proto channel: Make arrangements to send PADDING_NEGOTIATE</title>
<updated>2022-08-16T17:43:23Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-07-08T10:38:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0a1bffb047309d414d7fee05d56d95e99238e746'/>
<id>urn:sha1:0a1bffb047309d414d7fee05d56d95e99238e746</id>
<content type='text'>
This is actually a general facility for inserting locally-generated
cells into the outgoing stream.

It doesn't seem to be possible to do this without adding an additional
condition check to the reactor, since we need to insert it into the
right place in the stream, giving it priority over data, and only
using it up if there was room in the output.

We don't engage this machinery yet, because nothing sets
special_outgoing.
</content>
</entry>
</feed>
