mirrors/arti.git/crates/tor-proto/src/relay, branch arti-v2.4.0 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.4.0 2026-05-26T20:29:30Z proto: Remove TODOs about flushing pending data 2026-05-26T20:29:30Z Gabriela Moldovan gabi@torproject.org 2026-05-26T20:29:30Z urn:sha1:c508f738d0e4d4b8474acd1d7bef97d36d137984 We decided the reactor is the wrong place to handle this. See discussion in #2490 proto: Remove unused async 2026-05-20T14:45:30Z Gabriela Moldovan gabi@torproject.org 2026-05-14T17:42:12Z urn:sha1:46d45fee0d3c753741673c533ae54f1d8d97a4ad proto: Make TRUNCATE trigger a proto violation 2026-05-20T14:45:30Z Gabriela Moldovan gabi@torproject.org 2026-05-14T17:41:43Z urn:sha1:8d7e8680ae34f27a1e073cdc64b2d7e66645365b proto: Add some tests for DESTROY handling 2026-05-20T14:45:30Z Gabriela Moldovan gabi@torproject.org 2026-05-14T16:07:43Z urn:sha1:badf833178ebc170c5c487500c8b6d562c809c93 proto: Make do_create2_handshake() check EXTENDED2 was sent 2026-05-20T14:45:30Z Gabriela Moldovan gabi@torproject.org 2026-05-14T17:18:41Z urn:sha1:85cd56bd3bba8c70455b131a1973014bfae94890 This adds an extra assertion that ensures the relay reactor does in fact send an EXTENDED2 on its towards-the-client channel after receiving the CREATED2 response from the fake hop. This check is nice to have in general, but the main reason I'm doing this now is because for the DESTROY tests I'm about to add, I need the inbound MPSC queue (towards the client) drained of these handshake messages in order to check that the "next" cell we've sent is a destroy. I could've added some custom code to drain it just for the purposes of that test, but I think it's better to have `do_create2_handshake()` take care of it. proto: Extend helper to check that DESTROY was sent in both directions 2026-05-20T14:45:30Z Gabriela Moldovan gabi@torproject.org 2026-05-14T16:49:31Z urn:sha1:29ef39f0ecdaeca99db1974815f379d11daacad0 proto: Rename a test helper and adjust its docs 2026-05-20T14:45:30Z Gabriela Moldovan gabi@torproject.org 2026-05-14T16:38:32Z urn:sha1:052b0e27fc52564cd6eaf43594aeca8ba2f02e37 The new name is (hopefully) a bit more descriptive. I'm planning on extending this function soon to support checking if a DESTROY has been sent on the outbound channel too, so I'm tweaking the docs a bit in preparation for that. proto: Return the CircId from test handshake helper 2026-05-20T14:45:30Z Gabriela Moldovan gabi@torproject.org 2026-05-14T16:20:58Z urn:sha1:a73d8bdf7140501958b5f7b1bbabac0e6bd052c4 I'll soon need this for a DESTROY test. proto: Add test helper for sending AnyChanMsgs 2026-05-20T14:45:30Z Gabriela Moldovan gabi@torproject.org 2026-05-14T15:57:04Z urn:sha1:b89ebfb2e50dfefd5a86cefca5d57af2b580460b proto: Add a comment clarifying why we don't need to propagate DESTROY 2026-05-20T14:45:30Z Gabriela Moldovan gabi@torproject.org 2026-05-14T15:51:01Z urn:sha1:288f98a2e4770e1f68b395a97ca7947fc175e121