| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Provide facilities in ArgumnetStream for determining the column, and
add the field to all the error types up to and including ErrorProblem.
The value still needs to be propagated to ParseError, and printed there.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This will allow us to (1) move field name handling out of the argument
parser method, and also (2) add columns more easily.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We're about to have some functions return ArgumentError and some
ErrorProblem. We don't want to provide a conversion directly between
these types, so instead introduce a new type that will be convertible
to either.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-proto: allow comparison chain
See merge request tpo/core/arti!3342
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It was decided that the comparison chain was actually preferrable for
readability. So instead, we're just `allow`ing it until it stops being
a problem.
Signed-off-by: hashcatHitman <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There was a comparison chain in
`tor_proto::util::poll_all::test::ResolveAfter::poll` which was causing
a clippy warning. The lint in question, `clippy::comparison_chain`, was
a `clippy::style` lint in 1.85.1 and got moved to `clippy::pedantic` in
1.87.0 (see [rust-clippy!14219]).
Since some of us (like me) develop on MSRV, I'm fixing this lint now.
Gabi didn't have any strong opinions on whether I did it like this or
with an `allow` attribute, so I decided this was better since it means
we don't have to come back later just to remove the `allow`.
It should be noted that using a match like this can sometimes be a
performance regression (see [rust-clippy#5354] and [rust-clippy!6390]).
I would expect in this case the effect will be very little, if any, but
if tests in `tor_proto::util::poll_all::test` start taking much longer
and having an impact on CI or something, this could be why.
[rust-clippy!14219]: https://github.com/rust-lang/rust-clippy/pull/14219
[rust-clippy#5354]: https://github.com/rust-lang/rust-clippy/issues/5354
[rust-clippy!6390]: https://github.com/rust-lang/rust-clippy/pull/6390
Signed-off-by: hashcatHitman <[email protected]>
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
tor-netdoc: impl NormalItemArgument for Ipv4Addr and SocketAddr
See merge request tpo/core/arti!3343
|
| | |/ / /
| | | |
| | | |
| | | | |
AFAICT we don't have variant parsings for these things.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
arti-relay: Add mainloop and prepare to begin bootstrapping work
See merge request tpo/core/arti!3313
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
And remove one that we didn't need.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We'll add a `TorRelay` back in a following commit.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
hashx: Fix compilation on aarch64 with dynasm 4.0
Closes #2208
See merge request tpo/core/arti!3341
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The new conversion mechanisms in dynasm 4.0 make clippy unhappy
under aarch64.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
(Starting with version 4, dynasm wants something
that implements Into<u8>.)
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
CI: restrict cargo parallelism based on available memory
See merge request tpo/core/arti!3332
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is to mitigate https://gitlab.torproject.org/tpo/tpa/team/-/issues/42317
I added the 2h timeout (overriding the default 1h) for all jobs that
were cited as examples on that issue, and a couple others that looked
likely to be time-consuming.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* This reverts commit 8da606966e5213cada270fb64f896f69bab041dd.
* This reverts commit a3ac2080956b9295000bd7011c34111a6d5ce5a7.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
See https://gitlab.torproject.org/tpo/tpa/team/-/issues/42283
|
| |\ \ \ \ \ \
| |_|_|/ / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
arti: keys: Rework the output of `arti keys check-integrity`
Closes #2151
See merge request tpo/core/arti!3286
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|