| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
The script is a bit tricky because it needs to set arguments
correctly, use the right dependencies, treat packages differently
from scripts, and find all of the packages and scripts
in our repository.
|
| | | |
| | |
| | |
| | | |
Generator is more abstract, and expects a possible return or send type.
|
| | |/
| |
| |
| | |
For some reason this will soon be necessary with mypy.
|
| |\ \
| | |
| | |
| | |
| | | |
ci: upload 'shadow.chutney.data/' artifact in 'integration-chutney-shadow'
See merge request tpo/core/arti!2586
|
| | | |
| | |
| | |
| | | |
Set "1 week" since I see that it's used on another shadow artifact.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Final (ha!) clean-ups on rpc connect-string specs
Closes #1711
See merge request tpo/core/arti!2582
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
With all the fanciness we've built up here here, it seems that "connect
point" is a better term than "connect point".
|
| | |/
| |
| |
| |
| | |
(We've decided to make this change because these files are meant to
be written by humans.)
|
| |\ \
| | |
| | |
| | |
| | | |
CI: pip install chutney to get its dependencies
See merge request tpo/core/arti!2587
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
ci: use latest shadow commit
See merge request tpo/core/arti!2585
|
| |/ /
| |
| |
| |
| | |
The changes in https://github.com/shadow/shadow/pull/3428 should add
more details to the CI output of Shadow simulations.
|
| |\ \
| |/
|/|
| |
| | |
tor-chanmgr: revert `PendingChannelHandle` drop behaviour, and try to prevent problematic code paths
See merge request tpo/core/arti!2566
|
| | |
| |
| |
| | |
`upgrade_pending_channel_to_open`
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
An attempt to make sure that there are no code paths which forget to
remove a pending channel from the channel map.
This also adds error-level log messages and panics during debug builds
if a `PendingChannelHandle` is dropped without properly passing it to
`MgrState::remove_pending_channel` or
`MgrState::replace_pending_channel`.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit f85bc3cf849109aaa2c4da9fc8c06e7173a0543f.
There were some small conflcits in
`AbstractChanMgr::get_or_launch_internal`, so this wasn't a clean
revert.
|
| |\ \
| | |
| | |
| | |
| | | |
arti-rpcserver: Remove echo_on_session
See merge request tpo/core/arti!2549
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
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.
|