| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | | |
(Also fix a couple of typos)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Make sure that we can change elements, and we can reconstruct builders
that give us the same thing.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit implements the "metabuilder" pattern and the "builder
reconstruction" pattern for the ArtiConfig type.
I'm not 100% that this will be necessary, but it will certainly help
with testing.
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When we deserialize a configuration, we should reject unknown variables
(except when we have an explicit reason to allow them).
|
| | | | | |
| | | | |
| | | | |
| | | | | |
These don't need to be exposed any longer.
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I'm still not 100% sure this is the right move: should we encourage
app developers to always pick their own directories? Or should we
make it easy for them to use, well, `sane_defaults`?
This patch takes the second approach.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
UX improvements to with_coverage script
See merge request tpo/core/arti!143
|
| | | | | |
| | | | |
| | | | |
| | | | | |
The syntax is kinda minimal, but it seems to work okay.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Applies a suggestion from @trinity-1686a
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a slight kludge, but it helps a lot to keep track of what
exactly was tested for coverage.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If the -c flag is provided, we _continue_ with the previous
consensus_meta data (without deleting it).
If the -s flag is provided, we _skip_ generating the final report
(since we're going to be doing more profiling.)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If the directories are absent, then deleting them gives you a line
in stderr, even if you do "rm -f foo || true".
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now the shell is controlled by the presence of an -i flag, and can
be combined with a command.
This commit also adds usage messages and better reports for a couple
of kinds of setup errors.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Also improve comments and stdout slightly...
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This test seems unreliable on CI: we've got to disable them for now
so that we have a working CI system. The CI failure is #238; the
ticket to repair them is #244.
|
| |\ \ \ \ \ |
|
| | | | | | | |
|
| | | |/ / /
| |/| | | |
|
| |\ \ \ \ \ |
|
| | |/ / / / |
|
| |\ \ \ \ \ |
|
| |/ / / / / |
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | | |
|
| |/ / / / |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Also fix some commonwealth spellings that had slipped in.
|
| | | | | |
|
| |/ / / |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Rust nightly claims that Vec might get its own retain_mut method,
which would potentially conflict with the extension method we've
grabbed from the retain_mut crate. To solve this, we're calling the
method explicitly.
|
| | | | |
|
| |\ \ \ |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
params
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Try to make the tor_proto::circuit::begindir test more reliable.
See merge request tpo/core/arti!142
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I traced the problem here to the fact that sometimes "rx" in this
test would be dropped before the test was done. When "rx" is
dropped, the channel reactor shuts down, which in turn kills off the
circuit reactor.
This bug may exist in other cases in these tests. This patch may
fix one case of #238.
|
| | | | | |
|
| | |/ /
|/| |
| | |
| | |
| | | |
usage: with_coverage <command> [args...]: run <command> with [args...]
with_coverage : run bash
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Add and resolve clippy warnings in tor-events.
See merge request tpo/core/arti!138
|
| | |/ /
| | |
| | |
| | |
| | | |
Here we add the same array of clippy warnings as usual to the new
tor-event crate, and resolve the issues that triggered any of them.
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Further configuration refactoring
See merge request tpo/core/arti!137
|
| | | |
| | |
| | |
| | |
| | | |
This should be ergonomic than having to construct every section of the
configuration separately.
|
| | | |
| | |
| | |
| | |
| | | |
Doing this is necessary for reconfiguration support, and will help a lot
with testing, too.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This patch makes sure that for every* config type we have, the defaults
you get from a Builder match those you get from Serde, and that both
match the value that you get from arti_defaults.toml. Later down the
line I'll be adding some tests to keep these in sync.
* StorageConfig still has no defaults of its own, since we aren't so
sure we want other applications to use Arti's directories by default.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since these shell-variables are hardwired to use org.torproject.Arti as
the program name, it isn't appropriate to call them "app-specific".
If we someday reinstate APP_FOO, it should be based on a user-provided
application name.
|