mirrors/arti.git/Cargo.lock, branch arti-v0.0.2mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.22021-11-30T14:17:31ZOne more "cargo update" before the release.2021-11-30T14:17:31ZNick Mathewsonnickm@torproject.org2021-11-30T14:17:31Zurn:sha1:92c56eaa8399e3fc2e131185bcb9323e7c755a0fBump every crate by one patch version.2021-11-29T20:21:58ZNick Mathewsonnickm@torproject.org2021-11-29T20:21:58Zurn:sha1:eef81d9d570572b7a57a76de4003721c546856deRun "cargo update" to get latest versions.2021-11-29T19:52:53ZNick Mathewsonnickm@torproject.org2021-11-29T19:45:50Zurn:sha1:805e558045018663d0d47b5f30733c6ca19b86ac
Also fix a couple of warnings introduced by now-unneeded imports
with new ed25519 crate.
This is part of the process for releasing our next version.
Merge branch 'arti-client-config' into 'main'2021-11-22T15:43:22Zetator@eta.st2021-11-22T15:43:22Zurn:sha1:e35a8bf60e41157a5940823df5a33fde04b3e7ee
Further configuration refactoring
See merge request tpo/core/arti!137Merge commit '98f38dc' (arti!131) into HEAD2021-11-22T14:40:18Zetator@eta.st2021-11-22T14:40:18Zurn:sha1:ee2ec31ede1afbf1bf60e8aa33ca1455a8d30cb1
This commit message totally gives away the cursed way in which I use
git. branches? what are those?
Initial cut at a typed event framework for arti (arti#230).2021-11-22T14:39:38Zetator@eta.st2021-11-16T15:21:47Zurn: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.
Ensure that every section-level config type has a builder() function.2021-11-21T15:54:34ZNick Mathewsonnickm@torproject.org2021-11-21T02:00:20Zurn:sha1:aa83a5e38aba302efb2bd6b3eaf634ba9413d5d8Move top-level configuration downwards from `arti` to `arti-config`.2021-11-18T16:37:48ZNick Mathewsonnickm@torproject.org2021-11-17T19:16:55Zurn:sha1:5184f5ba84d76b75022fe6249ba18fe42807b1aa
To do this at all neatly, I had to split out `tor-config` from
`arti-config` again, and putting the lower level stuff (paths,
builder errors) into tor-config. I also changed our use of
derive_builder to always use a common error type, to avoid
error type proliferation.
Merge remote-tracking branch 'origin/mr/131'2021-11-18T00:26:28ZNick Mathewsonnickm@torproject.org2021-11-18T00:26:28Zurn:sha1:f0dc4a973d1db20dd69973f0e80d1fde1b66c175update dependencies2021-11-17T19:17:08ZTrinity Pointardtrinity.pointard@gmail.com2021-11-17T19:17:08Zurn:sha1:ab8e4cb6f02af7abb39380094a7cb59b7f108846