| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
APIs were added:
```
tor-units
tor-cell
tor-proto
tor-netdir
arti-client
```
Done with:
```
cargo set-version --bump patch -p tor-units
cargo set-version --bump patch -p tor-cell
cargo set-version --bump patch -p tor-proto
cargo set-version --bump patch -p tor-netdir
cargo set-version --bump patch -p arti-client
```
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Functional changes were made, but no APIs were added or broken:
```
tor-events (async_broadcast 0.6.0 -> 0.7.0)
tor-netdoc (signature 1 -> 2)
tor-guardmgr
arti-testing (config 0.13.4 -> 0.14.0)
tor-persist (breaking changes gated behind experimental feature)
fslock-guard (fix lockfile_has_path compilation on Windows)
```
Done with:
```
cargo set-version --bump patch -p tor-events
cargo set-version --bump patch -p tor-netdoc
cargo set-version --bump patch -p tor-guardmgr
cargo set-version --bump patch -p arti-testing
cargo set-version --bump patch -p tor-persist
cargo set-version --bump patch -p fslock-guard
```
|
| |
|
|
|
| |
`windows-targets 0.52.3` was yanked, so we need to run an update to pick
up `0.52.4`.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Without this, the nightly simd build fails.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
maint/fixup-features: Make part of the main workspace
Closes #1263
See merge request tpo/core/arti!1969
|
| | |
| |
| |
| |
| | |
This ties it into everything, so we run CI on it, have it in our main
lockfile, and so on.
|
| | | |
|
| |/
|
|
|
|
| |
Add comments where it's done automatically.
(There will be tests of the claims I'm making, in a later commit.)
|
| |
|
|
| |
Part of #1115
|
| | |
|
| |
|
|
|
|
|
| |
0.1.59 was yanked by upstream because it had a breaking change:
https://github.com/strawlab/iana-time-zone/pull/127
Update to 0.1.60.
|
| |
|
|
| |
We're just using fslock-guard now.
|
| |
|
|
|
|
| |
And export the type, so callers don't need to depend directly on
fslock_guard; many callers will need to own the returned value, not do
anything else with it.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
test-temp-dir: New crate
See merge request tpo/core/arti!1925
|
| | |
| |
| |
| |
| | |
Introduce the crate, move the code motion, and make minimal necessary
changes.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Upgrade to futures-rustls and rustls 0.22.
Closes #1179
See merge request tpo/core/arti!1919
|
| | |
| |
| |
| |
| |
| |
| | |
The futures-rustls crate has supplanted the async-rustls crate,
and it requires/embeds rustls 0.22.
Closes #1179.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
tor-hsservice: replay: Recover from partial writes
Closes #1207
See merge request tpo/core/arti!1920
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
I need this for state_dir (#1163, !1853).
I intend that this should be used for arti paths (#1092, #1193).
See also #1195.
Implements the spec in #1192 but doesn't connect it to anything yet.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Move state_dir to tor_persist and start to implement it
Closes #1205
See merge request tpo/core/arti!1913
|
| | |
| |
| |
| |
| | |
Bring in the fslock-guard crate and replace the Void in the structs.
(Separated out since this contains Cargo.lock churn.)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
And, instead of being a hidden module, it's a public experimental one.
I have feature-gated all the new dependencies since we probably want
to feature-gate this module in perpetuity, since some builds of Arti
won't need it.
Closes #1205
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This is not yet "correct", since it will rely on
https://github.com/brunoczim/fslock/pull/15
(Conceivably, it might be better to make the `fslock` crate rm-safe.)
|
| | |
|
| |
|
|
| |
Closes #1215
|
| |
|
|
|
| |
Provide the last modification time too, since we have it. This allows
handlers to things not contemplated by the convenience API.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This addresses a `TODO HSS` about deriving the `KeySpecifier`
implementation for client key specifiers.
Note that we no longer have a key specifier type for intro auth keys
(which are not supported anyway, see #1037).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
These crates had no changes previously, but they depend on crates
that had breaking changes themselves.
tor-linkspec
tor-hspow
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This crate doesn't have a meaningful public API, so it just gets a patchlevel bump:
arti
These crates had nonbreaking changes, and get a patchlevel bump:
tor-rtcompat
fs-mistrust
tor-llcrypto
tor-cert
|