| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Not uploading a descriptor because we suddenly found out there are no
IPTs isn't really an error.
Part of #1129
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This really should not (and cannot) happen under normal circumstances:
the task receiving the value cannot exit before the publisher (unless
there's a bug in that code).
Part of #1129
|
| |\ \
| | |
| | |
| | |
| | | |
Resolve some "TODO HSS" comments in arti, arti-client, tor-hsrproxy.
See merge request tpo/core/arti!1862
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
These are not "must fix before releasing onion services".
|
| | |/ |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
These crates had no changes previously, but they depend on crates
that had breaking changes themselves.
tor-linkspec
tor-hspow
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This crate doesn't have a meaningful public API, so it just gets a patchlevel bump:
arti
These crates had nonbreaking changes, and get a patchlevel bump:
tor-rtcompat
fs-mistrust
tor-llcrypto
tor-cert
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These crates have breaking changes on their own:
tor-error
tor-netdoc
tor-dirmgr
tor-keymgr
Because of the breaking change in tor-error, and the fact that
basically every crate publicly depends on tor-error (by implementing
ErrorKind), we need to call this a breaking change on all of the
following:
tor-config
tor-geoip
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-bytes
tor-hscrypto
tor-socksproto
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-testing
|
| |\
| |
| |
| |
| | |
Run fixup-features in preparation for release, and clean its output.
See merge request tpo/core/arti!1856
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
dirmgr: Make the `dir_mgr_config` method public
Closes #1175
See merge request tpo/core/arti!1847
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit makes the `dir_mgr_config` method of the `TorClientConfig`
struct public.
It might be questionable whether we should make this function public or
switch to a `TryInto` trait in general, which also seems like an even
Rustier solution Rustier solution.
Fixes #1175
|
| | |/
|/| |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
KeySpecifier improvements
Closes #1126, #1147, and #1151
See merge request tpo/core/arti!1851
|
| | | |
| | |
| | |
| | |
| | | |
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1851#note_2981473
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Swap the docs for new_any and arti_pattern to the right methods!
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1851#note_2981475
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This *is* the spec name.
|
| | | |
| | |
| | |
| | | |
Finishes arti#1151 item 10.
|
| | | |
| | |
| | |
| | | |
This also passes the information we'll need to populate extra_info.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This will make the macro work if call sites rebind Result.
|
| | | |
| | |
| | |
| | |
| | | |
The KeyInfoExtractor impl is still misindented but we'll change that
when we replace it.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now the only place that knows how to do all this is the one place in
the macro.
The indentation is -4 compared to previously, because we're going to
remove the wrapping with paste::paste! later. It's convenient to do
this reindent now, while we're rewriting it.
arti#1151 item 5.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This can only happen if we tried to parse an ArtiPath as the wrong
kind of KeySpecifier, which shouldn't happen very often.
If it does, the pattern isn't that interesting. Which is just as
well, since we're about to make it a bit harder to obtain it in the
place where this error is going to be constructed.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Where we wanted this, use derive_more::Constructor isntead.
arti#1151 item 6.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
So now .arti_pattern() is a trait method.
arti#1151 item 3.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
arti_prefix is no longer used. Abolish prefix too.
arti#1151 item 7.
Closes #1147.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a better API. The implementation has less monomorphisation.
arti#1151 item 2 and the patterns part of 4.
Closes #1126.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reduces monomorphisation.
arti#1151 item 4.
The commentary reflects a decision not to do arti#1151
item 9 (using fmt signature for to_component) at this time.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Part of arti#1151 item 10.
Discussion in
https://gitlab.torproject.org/tpo/core/arti/-/issues/1151#note_2977278
|
| | | |
| | |
| | |
| | |
| | | |
I'm not sure why the compiler doesn't complain about this already, but
it becomes "more" unused later.
|
| | | |
| | |
| | |
| | | |
This is going to expand and gain private helper methods.
|
| | | |
| | |
| | |
| | |
| | | |
We don't handle enums and we don't want to try.
Put this here as documentation of this intent.
|