| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
Version bumps for 1.3.1
See merge request tpo/core/arti!2650
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
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)
```
|
| |\
| |
| |
| |
| | |
Changelog for 1.3.1.
See merge request tpo/core/arti!2649
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
These were spotted by `cargo-semver-checks`.
|
| |/
|
|
|
| |
I tried to write this changelog according to the new guidelines from
arti!2616.
|
| |\
| |
| |
| |
| | |
Run fixup-features in preparation for release
See merge request tpo/core/arti!2648
|
| | | |
|
| | |
| |
| |
| |
| | |
The `bench` feature is only needed for running the benchmarks, and so
it's not covered by semver (much like the `testing` feature).
|
| | | |
|
| |/ |
|
| |\
| |
| |
| |
| | |
Run cargo update in preparation for 1.3.1 release.
See merge request tpo/core/arti!2647
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
`unicode-ident` recently changed their [license]
from "(MIT OR Apache-2.0) AND Unicode-DFS-2016"
to "(MIT OR Apache-2.0) AND Unicode-3.0".
[license]: https://github.com/dtolnay/unicode-ident/commit/36cccb825aef6f334cfb57afc82a728c3d2d652f
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| | |
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 are my notes and observations about the circuit and channel
reactors. In hindsight, this whole document is just stating the
"obvious"[^1], so I'm not sure if it's going to be useful for anyone
else. Also, since this isn't part of the code docs or tor-proto
crate-level docs, it's very likely to become outdated in the near
future.
At the end of the document, I also wrote a very rough KIST
implementation plan based on the discussion from #1712.
Closes #1747
[^1]: scare quotes because the "obvious" is only obvious after you've
stared at the circ/chan reactors for a while
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Start of host-side onion service PoW support
Closes #1691
See merge request tpo/core/arti!2609
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
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.
|
