mirrors/arti.git/crates/tor-proto, branch arti-v0.0.2 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.2 2021-11-29T20:21:58Z Bump every crate by one patch version. 2021-11-29T20:21:58Z Nick Mathewson nickm@torproject.org 2021-11-29T20:21:58Z urn:sha1:eef81d9d570572b7a57a76de4003721c546856de Mark a test as #[ignore] 2021-11-29T16:10:51Z Nick Mathewson nickm@torproject.org 2021-11-29T16:08:34Z urn:sha1:efe165acf3e7467ef31ebe6765c710d4d8c9322b This test seems unreliable on CI: we've got to disable them for now so that we have a working CI system. The CI failure is #238; the ticket to repair them is #244. add semicolons if nothing returned 2021-11-25T13:20:37Z Daniel Eades danieleades@hotmail.com 2021-11-25T13:14:05Z urn:sha1:db16d13df4779ac61005050dfe5ce05e3d5a1b5d More typo fixes that I forgot to save :( 2021-11-24T23:23:12Z Nick Mathewson nickm@torproject.org 2021-11-24T23:23:12Z urn:sha1:3e7e599a22972135f9c113a9a1e0757d22653481 Remove a couple more eprintln! calls. 2021-11-23T22:40:13Z Nick Mathewson nickm@torproject.org 2021-11-23T22:40:13Z urn:sha1:54de7f5cfd82eb04e1e119d1734eee2d6ee1176d Try to make the tor_proto::circuit::begindir test more reliable. 2021-11-23T15:50:20Z Nick Mathewson nickm@torproject.org 2021-11-23T15:50:20Z urn:sha1:672b11126267c525c78e2174d49889d0e9695606 I traced the problem here to the fact that sometimes "rx" in this test would be dropped before the test was done. When "rx" is dropped, the channel reactor shuts down, which in turn kills off the circuit reactor. This bug may exist in other cases in these tests. This patch may fix one case of #238. Make unreliable tor-proto tests more reliable (arti#238). 2021-11-18T16:06:53Z eta tor@eta.st 2021-11-18T15:40:18Z urn:sha1:075e663dcd740727ea6832581a38dc6ab0a36d53 The `bad_extend_*` failures were caused by bad test code in `bad_extend_test_impl` that used `futures::join!`; this meant that the reactor could receive the `Extended2` cell before it actually got the `ExtendNtor` request, which caused it to get (quite rightly) confused and close the circuit. Spawning a background thread which has a short delay before sending the `Extended2` cell seems to have alleviated this problem. `new_circ_create_failure` is similar; I think the reactor was getting dropped before it had a chance to flush out its `CreateFast` cell properly, because it had already gotten the result back (since the test code sends it indiscriminately). This was "fixed" in much the same manner as the other test: making it wait a bit before sending the result cell back. There seem to be other tests that use `futures::join!` (like `begindir`?), and use similarly erroneous patterns; I haven't gotten any to fail reliably enough to be able to debug them, though. Always use optimistic data for begindir connections. 2021-11-16T20:20:44Z Nick Mathewson nickm@torproject.org 2021-11-16T20:20:44Z urn:sha1:cc3efccdcc6e9ef8327f8544301a2ae0c5264830 Closes #226. tor-proto: Use tor-rtcompat macros for testing, not tokio. 2021-11-15T17:57:01Z Nick Mathewson nickm@torproject.org 2021-11-15T17:55:08Z urn:sha1:f92ad644c90480cd6ea738201119ce1e9fd40d8e Closes #222. tor-proto: Stop using async_test in halfstream.rs and sendme.rs 2021-11-15T17:12:53Z Nick Mathewson nickm@torproject.org 2021-11-15T17:12:53Z urn:sha1:787a99545872cc474a13d3961b647c1495b6631d Thanks to eta's refactoring, these tests no longer need to be async.