| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
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.25.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
```
We split them in the following categories:
* crates with no changes (no version bumps):
```
maint/changed_crates -v "arti-v$LAST_VERSION" 2>&1 >/dev/null | grep -i "no change" | grep -v '\(tor\|arti\)-'
oneshot-fused-workaround: No change.
test-temp-dir: No change.
caret: No change.
```
* crates that only have non-functional changes (bump the patch version):
- slotmap-careful
- fslock-guard
- hashx
- equix
- fs-mistrust
- safelog
- retry-error
* crates where APIs were broken (bump minor):
None
The bumps from this commit were created using this script:
```
PATCH="
slotmap-careful
fslock-guard
hashx
equix
fs-mistrust
safelog
retry-error
"
for crate in $PATCH; do
cargo set-version --bump patch -p $crate;
done
```
|
| |
|
|
|
|
|
|
|
| |
Done using
```
(cd crates/hashx/bench && cargo update)
(cd crates/equix/bench && cargo update)
```
|
| | |
|
| |
|
|
|
| |
The `bench` feature is only needed for running the benchmarks, and so
it's not covered by semver (much like the `testing` feature).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
I couldn't find a changelog, but judging from the commit history, it
looks like they've bumped their regex dep, updated their MSRV to 1.70,
replaced lazy_static with OnceLock internally.
|
| |
|
|
|
| |
According to the changelog, moving from 0.7.6 to 0.8.0 we get some new
constructors and breaking changes to various "general" APIs.
|
| |\
| |
| |
| |
| |
| |
| | |
tor-chanmgr: fix `get_or_launch` cancellation safety using deferred closure
Closes #1716
See merge request tpo/core/arti!2646
|
| | |
| |
| |
| | |
This shouldn't be needed anymore now that we use a `Defer`.
|
| | | |
|
| | |
| |
| |
| |
| | |
This contains the `Defer` type, which can be used to defer a closure
until the `Defer` is dropped.
|
| |\ \
| |/
|/|
| |
| | |
PoW: Consolidate feature flags into a single flag.
See merge request tpo/core/arti!2642
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This replaces the hs-pow, hs-pow-full, hs-pow-v1, pow-v1, and pow-full
features with a single hs-pow-full feature.
It's possible that in the future we will want to split different schemes
into different features, but we can do that when it comes up.
For now, having this as a single flag makes it clearer what's going on,
since the previous thing was not actually expressive enough to capture
some things we care about (like "at least one pow scheme is enabled"
that works in a future-compatible way).
This change is not semver breaking since it's a experimental feature.
Related: #1751
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
doc/dev/notes: cell-lifecycle: Describe the current state of things.
Closes #1747
See merge request tpo/core/arti!2637
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
These helpers seem potentially broadly useful, and only really
discoverable if they're here.
|
| | | |
|
| | |
| |
| |
| |
| | |
This includes the ability to generate a seed that does not share a head
with the previously used seed, which is generally what we want to do.
|
| | |
| |
| |
| |
| |
| |
| | |
I'm not particularly happy with the code that does the actual writing
out of the pow-params line, in particular the error handling there seems
very verbose. However, I don't know of a better way to structure it
given that APIs I'm working with.
|
| | |
| |
| |
| | |
Fixes: #1691
|
| | |
| |
| |
| | |
This currently is not implemented.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
If the channel request was cancelled, we should be able to retry
immediately. Additionally, the `kind()` of `RequestCancelled` is
`TransientFailure`, and I don't think it make sense for a transient
error to return a `retry_time()` of `Never`.
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
tor-keymgr: Remove dead code
See merge request tpo/core/arti!2638
|
| | | |
| | |
| | |
| | | |
This doesn't seem to be needed anymore.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Otherwise, we get a dead code warning when the `ctor-keystore` feature
is disabled.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The fields are never read but need to be present in order for the
dummy `KeyMgrBuilder` to have the same interface as the real one.
(We could of course manually implement the builder, or let the dummy
`KeyMgrBuilder` impl diverge from the real one, but for now let's leave
this as-is and simply mark the fields as unused).
|
| | | |
| | |
| | |
| | |
| | | |
We no longer have any dummy keymgr operations that return an error,
so this error type is unused.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This is not used anywhere (or exported publicly).
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
