| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Done via:
```
for crate in $(./maint/list-crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.39.0
done
```
|
| |
|
|
| |
This adds the lint to all our crates.
|
| |
|
|
|
|
| |
This function can only be called once within a program, so we can't call
it ourselves from a `TorClient`. The user must call it themselves, so we
should document this.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This struct is used to pass configuration parameters to the ChanMgr when
building it.
At the moment, it holds the ChannelConfig and RelayIdentities (feature
gated) which will be used in subsequent commits.
Note that relays do require RelayIdentities to build channels.
Signed-off-by: David Goulet <[email protected]>
|
| |
|
|
|
|
|
| |
We'll rely on a RelayIdentities to pass in the right keys to the ChanMgr
instead of the entire KeyMgr.
Signed-off-by: David Goulet <[email protected]>
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Done using the following:
```bash
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.38.0
done
```
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Fixes part of #2193.
(Edits from nickm: I selected the cases here that I could verify
were correct from immediate context.)
Edited-by: Nick Mathewson <[email protected]>
|
| |\
| |
| |
| |
| | |
Update to derive-deftly 1.6.0
See merge request tpo/core/arti!3525
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This has:
* Fixes to hygiene spans from the new modules feature, needed for
my WIP netdoc encoder derive.
* A substantially richer `${error }` construct.
|
| |\ \
| |/
|/|
| |
| | |
Add `KeyMgr` accessor to `TorClient`
See merge request tpo/core/arti!3442
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.37.0
done
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The non-{arti-,tor-} crates are:
```
./maint/list_crates | rg -v '^(tor|arti)'
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
hashx
equix
caret
fs-mistrust
safelog
retry-error
futures-copy
```
We split them in the following categories:
* crates with no changes (no version bumps): None
```
maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
```
* crates that only have non-functional changes (bump the patch version,
but not the dependend-on version):
- oneshot-fused-workaround
- slotmap-careful
- test-temp-dir
- fslock-guard
- equix
- caret
- safelog
- retry-error
* crates where functional changes were made, but no APIs were added or broken:
- hashx
- fs-mistrust
- futures-copy
* crates where APIs were broken (bump minor): None
The bumps from this commit were created using this script:
```
PATCH_NF=(
oneshot-fused-workaround
slotmap-careful
test-temp-dir
fslock-guard
equix
caret
safelog
retry-error
)
PATCH="
hashx
fs-mistrust
futures-copy
"
./maint/bump_nodep "${PATCH_NF[@]}"
for crate in $PATCH; do
cargo set-version --bump patch -p $crate;
done
```
|
| |\ \
| | |
| | |
| | |
| | | |
arti-client: Fix typo
See merge request tpo/core/arti!3504
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now that `vanguard_config()` is no longer conditional, we can handle
`vanguard_config` just like other accessors. This is a breaking change,
but I think we may as well make this change while we've already made
another breaking change in the previous commit.
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| | |
These are all aimed at figuring out in more detail what's going on
in #2079 and related issues.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
arti/arti-client/tor-hsservice: Support disabling onion services in the config
Closes #2133
See merge request tpo/core/arti!3253
|
| | | |
| | |
| | |
| | | |
We don't need to modify semver files for newly added methods.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Combined with the previous commit, this completes my second attempt at
correctly handling the semver files.
tor-hssservice:
I removed the extra bit at the end of the first line explaining the
semantics of the new return type, since the important part is really
just the fact that the return type changed. The semantics are documented
in the methods themselves.
arti-client:
Same as above, but I also removed the `client` module prefix since the
`client` module isn't actually public, so to external crate users the
broken type is directly in the crate root.
Removed old "used in the public API of this crate" line.
Added lines referring to the 2 breaking changes we re-export from
tor-hsservice.
arti-ureq:
Removed old "used in the public API of this crate" line.
Added lines referencing every breaking change in arti-client. This MIGHT
be wrong, but I think this is correct because we re-export arti-client
as a whole.
Signed-off-by: hashcatHitman <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | | |
If I understand correctly, the breaking changes propagate like this.
Signed-off-by: hashcatHitman <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Might be too verbose... unsure.
Signed-off-by: hashcatHitman <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There is no longer a hard error anywhere for trying to launch a service
which is disabled in the config. Instead, it always means returning
`Ok(None)`.
The axum and hyper examples were updated again as a consequence.
Signed-off-by: hashcatHitman <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When a service is disabled in the config, `arti::onion_proxy::Proxy`
handles it gracefully, and
`arti_client::client::TorClient::launch_onion_service_with_hsid` and
`arti_client::client::TorClient::launch_onion_service` both hard error.
The axum and hyper examples were updated again as a consequence.
Signed-off-by: hashcatHitman <[email protected]>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Hidden services disabled in the config are now handled more gracefully
by arti/arti-client, before the hard error occurs.
The axum and hyper examples were updated as a consequence.
Signed-off-by: hashcatHitman <[email protected]>
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
`arti-client`: Move `create_onion_service()` to `InertTorClient`
See merge request tpo/core/arti!3435
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | |/
| |/|
| | |
| | | |
Part of #2118.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This has the meta attributes with optional values feature and also
hygiene rework for modules.
The breaking changes don't break arti.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Bump derive-deftly to 1.4.0
See merge request tpo/core/arti!3448
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will let us use the new modules feature.
There are no breaking changes to beta features in 1.4.0.
|
| |/ / /
| | |
| | |
| | | |
Run maint/add_warning
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
arti-client: Update `ARTI_CLIENT_RELEASE_DATE`
See merge request tpo/core/arti!3413
|
| | | |
| | |
| | |
| | |
| | |
| | | |
```bash
./maint/update-release-date
```
|
| |/ /
| |
| |
| |
| |
| |
| | |
```bash
readarray -t publish < <(cargo metadata --format-version 1 | jq -r '.packages[] | select((.id | startswith("path+file:///")) and (.rust_version != null) and (.publish == null or .publish == true or .publish != [])) | .name')
for package in "${publish[@]}"; do echo "$package:"; cargo set-version --bump minor -p "$package"; done
```
|
| | | |
|
| | | |
|
| |/ |
|
