mirrors/arti.git/crates/tor-events, 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-30T14:12:51Z Merge branch 'readme_fixes' 2021-11-30T14:12:51Z Nick Mathewson nickm@torproject.org 2021-11-30T14:12:51Z urn:sha1:3b072c542064002f71d2a6a6a9fc22a83dbe5962 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 run ./maint/readmes.sh 2021-11-29T11:29:28Z dagon dagon12@tutanota.com 2021-11-29T11:29:28Z urn:sha1:d5c48c616fd40313f0428d14bae97419ae3dac95 add semicolons if nothing returned 2021-11-25T13:20:37Z Daniel Eades danieleades@hotmail.com 2021-11-25T13:14:05Z urn:sha1:db16d13df4779ac61005050dfe5ce05e3d5a1b5d Remove a couple more eprintln! calls. 2021-11-23T22:40:13Z Nick Mathewson nickm@torproject.org 2021-11-23T22:40:13Z urn:sha1:54de7f5cfd82eb04e1e119d1734eee2d6ee1176d Add and resolve clippy warnings in tor-events. 2021-11-22T16:49:31Z Nick Mathewson nickm@torproject.org 2021-11-22T16:49:31Z urn:sha1:94790016495c61e2913d645fde51274e963437b1 Here we add the same array of clippy warnings as usual to the new tor-event crate, and resolve the issues that triggered any of them. Initial cut at a typed event framework for arti (arti#230). 2021-11-22T14:39:38Z eta tor@eta.st 2021-11-16T15:21:47Z urn:sha1:98f38dc186212624d377653ed8ecf3c47366c3ad This implements a basic typed event broadcast mechanism, as described in arti#230: consumers of the new `tor-events` crate can emit `TorEvent` events, which others can consume via the `TorEventReceiver`. Under the hood, the crate uses the `async-broadcast` (https://github.com/smol-rs/async-broadcast) crate, and a `futures::mpsc::UnboundedSender` for the event emitters; these are glued together in the `EventReactor`, which must be run in a background thread for things to work. (This is done so event sending is always cheap and non-blocking, since `async-broadcast` senders don't have this functionality.) Additionally, the `TorEventKind` type is used to implement selective event reception / emission: receivers can subscribe to certain event types (and in fact start out receiving nothing), which filters the set of events they receive. Having no subscribers for a given event type means it won't even be emitted in the first place, making things more efficient.