| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |\ \
| | |
| | |
| | |
| | | |
Move RPC documents into a new location
See merge request tpo/core/arti!2581
|
| |/ /
| |
| |
| | |
This will be the start of an mdbook document.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Sketch RPC server and superuser operations.
Closes #1702
See merge request tpo/core/arti!2563
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The main purpose of this commit is to RPC servers to configure
connect points individually, while allowing clients to look at a
configuration location that is full of multiple connect points.
This change permits us to discard allow_missing_file, which is nice.
This commit still pretends that the file extension is "json";
that will be fixed in #1711.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The most salient change here is that _everything_, including the
default connect string, is a configuration option, so that
`--system-arti` (hypothetical) can override it.
In order to make the default connect file locations
behave like regular options, I've added a `allow_missing_file`
sub-option that makes the absence of a file tolerable.
There is a behavioral change here: Specifying your own `rpc.listen`
entries in the arti.toml _does not_ disable checking the default
connect file locations.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | | |
Co-authored-by: Ian Jackson <[email protected]>
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
tor-persist: Explain why colons will never be valid slug chars.
See merge request tpo/core/arti!2576
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Update P101 numbers for Q3-2024.
See merge request tpo/core/arti!2571
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fix various python warnings
See merge request tpo/core/arti!2579
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This has a little complexity since beautifulsoup4 is fairly well
duck-typed, but it also has type annotations to describe its
duck-typing.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
mypy rightly complained that our context.arti_process could be None.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The `black` formatter did most line wrapping for us, and we accept
its default of 88 characters there, but for comments and docstrings
(which black doesn't wrap) we allow up to 99 characters.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
(Python coding style guide and lint tools deprecate it,
even if your font distinguishes l, 1, I, and |.)
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Due to precedence, both work the same, but the former is preferred.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It no longer reflects our current API, refers to no-longer-extant
bugs, and was never a terribly good example of what you were
supposed to do with RPC.
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
doc/dev/notes/vanguards: Use the new circuit stem terminology.
Closes #1479
See merge request tpo/core/arti!2410
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
As per #1479
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
As per #1479
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is the first step towards clarifying the questions from !2230.
Corresponding torspec changes: https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/282
Part of #1479
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
"Circuit stubs" are now called "circuit stems".
We are also replacing the STUB/STUB+ terminology (STUB/STUB+ circuits
are now called NAIVE/GUARDED).
Part of #1479
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Run "black" to reformat all our python
See merge request tpo/core/arti!2578
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
"Black" is an "opinionated" python formatter, whose opinionatedness
is somewhat in the spirit of rustfmt.
This MR runs black with default settings on all of our python code
in Arti. It was produced by the following commands
```
# Everything in python/
black python/
# Everything with a .py extension
fd '.py$' -X black
# Everything with a python shebang.
git grep -l '#! */usr/bin/env *python' | xargs black
```
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
rpc: Move `rpc:release` method to apply to all object-ids.
Closes #1663
See merge request tpo/core/arti!2573
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This commit removes the separate function for asking whether to
bypass the dispatch code. Instead, it gives the "invoke with
bypass" function an error to return when no dispatch is warranted,
and moves the whole responsibility for method dispatch or
non-dispatch back into tor-rpcbase.
I had to add an ObjectId argument to `invoke_rpc_method` to make
this work, but that's probably a good thing.
Additionally, this commit tweaks the derive-deftly macro to prevent
you from asking for dispatch bypass on special methods, where it
isn't implemented (and doesn't really make sense).
|