mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.5.0 2022-05-11T12:26:35Z 2022-05-11T12:26:35Z eta tor@eta.st 2022-05-11T12:26:35Z urn:sha1:864fd03917a0409c6a0380c258d96252359a559b - arti#445 highlighted the lack of good documentation around Arti's multiple runtime support, as well as it being difficult to determine what runtime was actually in use. - Improve the documentation to solve the first problem. - To solve the second problem, make Runtime require Debug (which is arguably a good idea anyway, since it makes them easier to embed in things), and print out the current runtime's Debug information when arti is invoked with `--version`. - (It also prints out other Cargo features, too!) fixes arti#445 2022-03-30T12:55:58Z Nick Mathewson nickm@torproject.org 2022-03-30T12:55:58Z urn:sha1:700e491813f84d76446193aef7121a329b774717 2022-02-25T23:33:44Z trinity-1686a trinity@deuxfleurs.fr 2022-02-25T23:33:44Z urn:sha1:f06b25601006ba42c427349837dca6d5634bc718 2022-01-26T19:06:58Z Nick Mathewson nickm@torproject.org 2022-01-26T18:27:42Z urn:sha1:dec2c4ee639c3a3584f416116f286231d0a59df8 This took some refactoring, so that I wouldn't need to define 9 different versions of the function. It also required that we change the behavior of test_with_all_runtimes slightly, so that it asserts on _any_ failure rather than asserting on most but returning Err() for others. That in turn required changes to a few of its callers. There's probably a better way to do all of this macro business, but this is the best I could find. 2021-11-04T15:04:59Z Nick Mathewson nickm@torproject.org 2021-11-04T15:04:59Z urn:sha1:83d9f2299ebfb4355ced1b3111b3e1f4bff62e43 2021-10-26T17:13:46Z Nick Mathewson nickm@torproject.org 2021-10-26T17:12:41Z urn:sha1:e64177d97e3623474f042df45efefa46d17a45a0 These are my fault; I merged the wrong version of !102. :p 2021-10-26T15:33:23Z eta tor@eta.st 2021-10-25T13:19:07Z urn:sha1:e8419abd2579960d59cfe418adc15cdccd20b154 Instead of racily advancing time forward, this commit attempts to rework how WaitFor works, such that it makes advances when all sleeper futures that have been created have been polled (by handing the MockSleepRuntime a Waker with which to wake up the WaitFor). The above described mechanics work well enough for the double timeout test, but fail in the presence of code that spawns asynchronous / background tasks that must make progress before time is advanced for the test to work properly. In order to deal with these cases, a set of APIs are introduced in order to block time from being advanced until some code has run, and a carveout added in order to permit small advances in time where required. (In some cases, code needed to be hacked up a bit in order to be made properly testable using these APIs; the `MockablePlan` trait included in here is somewhat unfortunate.) This should fix arti#149. 2021-09-08T15:28:31Z Daniel Eades danieleades@hotmail.com 2021-08-30T07:52:16Z urn:sha1:fb3b8b84b5709ebe8a29051c43b82c4eef85decc 2021-08-27T13:53:09Z Nick Mathewson nickm@torproject.org 2021-08-27T13:53:09Z urn:sha1:557a0ff40b3731d4690767de27010bbeff08777d This will cause some pain for now, but now is really the best time to do this kind of thing.