| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
No functional changes, this is just code motion.
This helps organize the code in `arti/src/lib.rs` a bit. It now only
contains the argument parsing and various other setup, and all the
subcommands are contained in separate modules.
|
| | |
| |
| |
| | |
No functional changes, this is just code motion.
|
| | |
| |
| |
| |
| | |
The implementation for `arti proxy` will soon be relocated to this new
module.
|
| |\ \
| | |
| | |
| | |
| | | |
rpc: Fix argument type for rpc_session_get_rpc_proxy_info
See merge request tpo/core/arti!2409
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Without this, we get a panic on startup when running with RPC!
(This stresses the need for an integration test for RPC;
I will start writing that after the Python wrapper lands.)
|
| |/ /
| |
| |
| | |
We don't support this yet, see #727.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
tor-hsservice: Improve descriptor publisher status reporting
Closes #1216 and #1572
See merge request tpo/core/arti!2397
|
| | |/
| |
| |
| | |
We now log the onion service status on change.
|
| |/ |
|
| |
|
|
|
| |
Ticket #1509 will probably get rid of this constant,
but for now we may as well put it in one place.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Renamed address to tcp_address, and made it optional, so that later
we can have a unix_path, etc.
On deser side, add support for unrecognized listener types.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This belongs in a spec, but adding things to a spec is slow and
fraught. Instead we'll put it here for now and move it later.
There are some XXXXs about "finalizing" the design that we need to
resolve before we can merge !2373 and implement stream creation in
`arti-rpc-client-core`.
|
| |
|
|
|
|
|
|
| |
Currently this behaves the same as get_proxy_info,
but this may change in the future, if we introduce RPC-unsuitable
proxy ports.
(Also rename the get_proxy_info method to avoid x_ prefix.)
|
| |
|
|
|
|
|
|
| |
This effectively reverts 71e3d52f5aeb34ca7bca80053079a8c7505b99ac,
which was itself a revert of disabling this test the first time.
Sadly it still doesn't seem to be reliable. We have agreed on IRC to
disable it for now.
|
| |\
| |
| |
| |
| |
| |
| | |
arti: Make the config watcher debounce interval configurable.
Closes #1589
See merge request tpo/core/arti!2387
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, the `reload_cfg::test::watch_multiple` test would take about
3s to run. This test modifies 3 files and waits for the corresponding
`reconfigure()` events to fire. Because of the
`sleep(DEBOUNCE_INTERVAL)` in `run_watcher`, it would wind up waiting
for about 1s for each of them.
This makes the event debouncing optional, and disables it in the tests.
Closes #1589
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
arti: Write the test config atomically.
Closes #1549
See merge request tpo/core/arti!2375
|
| | |
| |
| |
| | |
This reverts commit ececf6be2eaffc201666cd3413dc19c025be66de.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The flakiness from the `watch_single_file` test was caused by the race
between the config write, and the fake SIGHUP "signal" sent on
`sighup_tx`: sometimes, the sighup would get handled between creating
the config file and writing its contents. In those cases, the config
received in `TestModule::reconfigure` would be `Default::default()`,
which caused an assertion to fail (because the test is expecting to
receive the `ArtiConfig` it wrote to disk).
Closes #1549
|
| | |
| |
| |
| | |
Nothing uses this yet.
|
| | |
| |
| |
| |
| |
| | |
Including testing that uncommenting the example generates a config
with tracking enabled, and that the example low_water is the default
value for the example max.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Tests are not entirely trivial and will come in a moment.
|
| | |
| |
| |
| |
| |
| | |
* In arti, memquota simply turns on in memquota arti-client
* In arti-client, add an (unconditional) dependency on tor-memquota,
and have the memquota feature turn on the feature in tor-memquota.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Done using:
```
cargo set-version --bump patch -p arti
```
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.22.0
done
```
|
| | | |
|
| | |
| |
| |
| | |
The `restricted-discovery` feature is reachable from `experimental`.
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
| |
This sets `COLUMNS` to a large value to prevent line wrapping.
Prompted by https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2370#note_3067346
Closes #1574
|
| |
|
|
|
|
| |
These file paths occupy more than 2 lines on some platforms.
See also the motivation behind 2b8a7a196b3ea5cd8350dd77f5e5120fed8521e0
|
| |
|
|
|
|
|
|
|
| |
This allows us to reenable the `arti hsc` tests, which were previously
disabled due to flakiness (see #1496).
The `help` test bit rotted a bit, so I had to tweak its expected output.
Closes #1496
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Having this in the `tor-async-utils` crate prevents us from doing both
of the following without introducing a circular dependency:
* using it in `tor-rtmock` (which we currently do, particularly in
tests).
* using `tor-rtmock` to test things in `tor-async-utils`. We don't do
this yet, but it is generally sensible to do so. In particular we
want to move the `stream_peak` module there, which is currently tested
with `tor-rtmock`.
Moving this into its own crate avoids this circular dependency.
|
| |\
| |
| |
| |
| |
| |
| | |
RPC: Add experimental method to list SOCKS proxy addresses.
Closes #1523
See merge request tpo/core/arti!2359
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
(This is a bit trickier than I would like, but it ensures that we
never return a "not initialized yet" code.)
|
| | | |
|
