| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
Run cargo update in preparation for release tomorrow
See merge request tpo/core/arti!1000
|
| | | |
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Disable ./maint/check_doc_features
Closes #601
See merge request tpo/core/arti!985
|
| |/
|
|
|
|
|
|
|
|
| |
This is a fair amount of manual work to keep in sync. I would like to
disable this, at least as a mandatory check, for now.
Fixes #601 (the request for it to become non-blocking).
The underlying issue is #581 and remains open.
Co-authored-by: trinity-1686a <[email protected]>
|
| |\
| |
| |
| |
| |
| |
| | |
Export SRV information from NetDoc up to NetDir, and TimePeriod from NetDir
Closes #686
See merge request tpo/core/arti!987
|
| | | |
|
| | |
| |
| |
| |
| | |
It's cute, but I don't think it will help performance, and I'm
undecided about whether the semantic implications are true.
|
| | | |
|
| | |
| |
| |
| |
| | |
This may be temporary if we wind up converting to CtByteArray,
but for now it's good to be terse.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This logic is a bit tricky, so I've tried to document it and add
fairly good tests. The silver lining is that the external API for
all of this logic will make it invisible and hidden.
There are some cases where I added functions that I think might
eventually get lowered into MdConsensus: But I don't want to lower
too much right now, since the convention for our netdoc accessors is
that they are fairly unsophisticated, and they show you the document
as it is.
Closes #686
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
These are deliberately unsophisticated accessors, in that they return Option<>
rather than filling in missing values with the documented
fallbacks. It seems better to leave a way to distinguish the absent
case in the API.
|
| | |
| |
| |
| |
| | |
This breaks some experimental APIs, but since they are experimental
no semver note is needed.
|
| |/ |
|
| |\
| |
| |
| |
| | |
Fix typos
See merge request tpo/core/arti!996
|
| |/ |
|
| |\
| |
| |
| |
| | |
maint: replace llvm-tools-preview with llvm-tools
See merge request tpo/core/arti!993
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
This commit replaces all occurrences of `llvm-tools-preview` with
`llvm-tools`, because it became a stable feature with Rust 1.60, thereby
making the `-preview` prefix obsolete. Beside this, `llvm-tools-preview`
is a redirection to the latter one anyway.
However, it does not work the other way around. At the moment, it is not
possible to execute the `maint/coverage` script on a NixOS system,
because the rustup component list only includes `llvm-tools`, but not
`llvm-tools-preview`, thereby making this change necessary.
|
| |\
| |
| |
| |
| |
| |
| | |
Fix clippy warnings from Rust 1.67
Closes #749 and #748
See merge request tpo/core/arti!992
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Clippy now complains about `let _ = (expr_producing_a_future);`,
which is probably smart, since maybe you wanted to await that future
and ignore the result. So it seems that the right way to get rid of
an unwanted Receiver is now to drop it explicitly.
Closes #749
|
| | |
| |
| |
| |
| | |
In both cases I think it's fine to panic; but it's best to do so
explicitly.
|
| | |
| |
| |
| |
| | |
This panics on error, and we're fine with a panic on misbehavior in
tests.
|
| | |
| |
| |
| |
| | |
Clippy now warns about these; I'm not sure how these warnings snuck
up on us.
|
| |/
|
|
|
|
|
|
| |
This warning kind of snuck up on us! (See #748) For now, let's
disable it. (I've cleaned it up in a couple of examples, since
those are meant to be more idiomatic and user-facing.)
Closes #748.
|
| |\
| |
| |
| |
| | |
Update C Tor specific numbers for s101-o3 for January
See merge request tpo/core/arti!991
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
Upgrade toml to version 0.6.
See merge request tpo/core/arti!989
|
| | |
| |
| |
| |
| |
| |
| | |
This required rewriting some of our error handling code in
command-line processing, since the toml crate now displays and
reports errors differently. (Admittedly, this code still is kind of
ugly, but at least it is nicely hidden.)
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Implement tor-hscrypto
Closes #684 and #742
See merge request tpo/core/arti!980
|
| | | |
| | |
| | |
| | |
| | |
| | | |
It turns out that the credential is only calculated as an
intermediate result in order to blind keys and produce the
subcredential. As such, it has no need to leave the hscrypto module.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, the offset was set to 12 hours unconditionally (like the
spec says). But based on a conversation on tor-dev, it seems that
the offset should actually be 12 times the voting interval.
I'm also opening an MR to change the spec.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
(I have squashed the fixes for these warnings into the earlier
commits in this branch, so it will look like I did everything right
the first time.)
|
| | | |
| | |
| | |
| | |
| | | |
This implementation was made based on the specification, and then
validated against itself, and against C Tor.
|
| | | |
| | |
| | |
| | |
| | | |
This required some API tweaks, which is probably to be expected;
these time periods are a wonky kind of thing.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
