| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This handle contains all of the details required to remove or replace a
pending channel entry from the channel map.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
These methods on `MgrState` acquire a lock, and it's easy for calling
code to also try to acquire the same lock within the closure, causing a
deadlock. It's better to not expose these methods.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Best reviewed with the '-w' flag to hide whitespace changes.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This moves most of the channel map logic from
`AbstractChanMgr::choose_action` to `MgrState::request_channel`.
This is working towards being able to remove
`MgrState::with_channels{,_and_params}`.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
rtcompat: Fix android compilation in `general`
See merge request tpo/core/arti!2553
|
| | | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously I had assumed that `std::os::linux` also existed on
android, based on the documentation of
`std::os::linux::net::SocketAddrExt`. That is not, however, true.
This should fix the `check-targets` CI job.
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
RPC: Sketch for how connect strings work
See merge request tpo/core/arti!2439
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | | |
This is based on conversations with Diziet,
and is a followup from arti!2388 and arti!2429.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
tor-config: Use a polling watcher on non-windows platforms that don't have inotify.
Closes #1644
See merge request tpo/core/arti!2547
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Part of #1644
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This enables us to make use of the unfortunately-necessary test-specific
code path.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When testing, compare the contents of the files too, not just their
mtime Otherwise, because the polling backend detects changes based on
mtime, if the test creates/writes files too fast, it will fail to notice
changes (this can happen, for example, on a tmpfs).
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The default is 30s, which feels a bit too long.
Also, when testing, we use a much shorter interval.
This is meant to be a temporary solution, so we hard-code the interval
rather than make it configurable.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
inotify.
On windows and platforms that support inotify (i.e. linux and android),
we continue using the recommended watcher. On platforms that use kqueue,
we switch to a polling watcher to work around a [notify bug] that
manifests when using a non-recursive watcher to watch a directory.
This commit is best reviewed with `git diff --ignore-all-space`.
Closes #1644
[notify bug]: https://github.com/notify-rs/notify/issues/644
|
| | | | | | | |
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | |
| | | | | |
This type will soon become platform-dependent, so I am preemptively
adding a type alias.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
general::SocketAddr: Specify and implement string representations.
Closes #1681
See merge request tpo/core/arti!2519
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
(This turned up another place where we need documentation.)
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The fuzzer makes sure that whatever we can parse, we can format into
an object that is parsed in the same way.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This matches our parsing, and our general rule that our parser
defers to SocketAddr::from_pathname.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Needed for tests.
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | | |
Closes #1681.
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
arti: remove 'relay' subcommand and 'arti-relay' dependency
See merge request tpo/core/arti!2542
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
memquota features, preparation
See merge request tpo/core/arti!2545
|
| | | | | |
| | | | |
| | | | |
| | | | | |
(fmt)
|
| | | | | |
| | | | |
| | | | |
| | | | | |
It's not documented anywhere ATM. I will do that in a followup MR.
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will allow us to make `tor-memquota/memquota` enabled by default,
without forcing it to be compiled in everywhere.
I don't change that in this MR, though.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | | |
rpc spec: Start to document method naming convention
Closes #1678
See merge request tpo/core/arti!2539
|
| | | | |
| | | |
| | | |
| | | | |
Closes #1678.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
All but one of our current methods follows this convention,
and we're about to rename it.
|