| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
We're going to call from_net_params from the parse2 trait impl.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The rest of types::misc does this. We should probably follow suit for
consistency. Also we're going to want to add soemthing here.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This omission seems like an oversight. I thought I wanted it, but it
turns out I don't - but I think it should still be there.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
This seems to have been overlooked.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-proto: Relax XON/XOFF receive limits
See merge request tpo/core/arti!3360
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
tor-dirserver: General refactoring of various TODOs
See merge request tpo/core/arti!3285
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This commit renames the schema module to the database module in order
to perform better error handling while redesigning the API.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
doc/hss.md: Add basic usage instructions for arti hss
Closes #2108
See merge request tpo/core/arti!3357
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This will make the doc render nicely outside of GitLab too.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Closes #2108
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
proto: Remove an allow that is no longer needed
See merge request tpo/core/arti!3356
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
doc: Add relay task dev notes
Closes #2216
See merge request tpo/core/arti!3358
|
| | | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Closes #2216
Signed-off-by: David Goulet <[email protected]>
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
CI: split rust-recent script and jobs
See merge request tpo/core/arti!3352
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Hopefully these are now sufficiently small to fit into the default 1h
timeout.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This job is still expensive and a bottleneck. "cargo test" is the
slowest part, and experimentally doesn't seem to generate artifacts used
in the other steps nor reuse artifacts genrated in other steps.
Splitting it out to its own job exposes more parallelism.
"cargo test" is also more prone to flakiness than the other commands,
which just build code without running it. Isolating the flakiness is
helpful when we need to retry. (Though of course ultimately we want to
eliminate such flakinesss)
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
There's probably not much benefit to building these on rust-latest in
addition to rust-recent; incompatibilities with rust-latest should be
found in rust-latest-dev-test. Let's save the template complexity
and CI cost.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
rust-recent (and rust-latest, for runs on the main branch) is one of our
longer jobs, particularly in the 'build' CI stage, making it a
bottleneck for starting the 'test' stage.
The job does quite a bit of work, some of it with very little overlap
due to use of different cargo build profiles.
This commit splits the job roughly by build-profile, so that the work
done with each build profile can proceed in parallel.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
proto: Move celltypes out of client
See merge request tpo/core/arti!3355
|
| | | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | | |
Some of these are relay-specific, so it makes more sense to pull this
into a top-level module.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
proto: Stop using tunnel IDs in relay reactor.
See merge request tpo/core/arti!3353
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Using a tunnel ID here doesn't make much sense right now, because we
don't yet support exit-side conflux (and when we will, it's unclear
whether the concept of "tunnel" will be applicable, especially if we
refactor things such that multi-path circuits are handled without a
ConfluxSet-like type like we have for clients).
This change forces us to stop using the client-specific
`unwrap_or_shutdown` (because this macro expects `self` to have a tunnel
ID), but IMO that is okay.
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
proto: Use a small vec for the hop list.
See merge request tpo/core/arti!3354
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
We can optimize for the general (N <= 3) case, and avoid a heap
allocation.
|