| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Done with:
```
CRATES="
tor-basic-utils
tor-async-utils
tor-error
tor-config
tor-events
tor-units
tor-geoip
tor-rtcompat
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-llcrypto
tor-protover
tor-bytes
tor-hscrypto
tor-hspow
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-relay-selection
tor-congestion
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-bench
arti-testing
"
for crate in $CRATES; do
cargo set-version -p "$crate" 0.17.0
done
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These have all had backward-compatible changes.
Generated with:
```
cargo set-version --bump patch -p fs-mistrust
cargo set-version --bump patch -p test-temp-dir
cargo set-version --bump patch -p fslock-guard
cargo set-version --bump patch -p hashx
cargo set-version --bump patch -p equix
cargo set-version --bump patch -p caret
cargo set-version --bump patch -p safelog
cargo set-version --bump patch -p retry-error
```
|
| | |
|
| | |
|
| |
|
|
|
| |
Change Path::display to this new function, in call sites where it's
being used for a diagnostic.
|
| |\
| |
| |
| |
| |
| |
| | |
deny clippy::unchecked_duration_subtraction
Closes #1304
See merge request tpo/core/arti!2008
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
```
|
| |/
|
|
|
|
|
|
|
| |
The test fails on Windows systems for two reasons:
- File separator \ is printed in error message instead of expected /
- Temporary files are located within home directory, which is anonymized
Test failure can be provoked on Linux as well by setting TMPDIR to point
to a directory within HOME.
|
| |
|
|
|
| |
Actually, we want to test handling of the string with whatever the
extension would be, if it changed.
|
| |
|
|
|
|
|
| |
And replace ".lock" with it.
Now the only place that the "lock" extension this is still present as
a literal is in a test.
|
| |
|
|
|
|
| |
And replace "lock" with it. This is the first half of not open-coding
this; the sites where the literal string is ".lock" are in the next
commit, to help avoid the slip of using the wrong constant.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Now ee consistently use "instance id" or "instance identity" (or,
where unambiguous, "id"), to mean the identity of an instance within a
kind, and "instance" to refer to the whole thing including the kind.
|
| | |
|
| | |
|
| |
|
|
| |
We're going to get more call sites.
|
| | |
|
| |
|
|
|
|
|
|
| |
Slug is the general type. Instance kinds are slugs too. We need a
word for the slug-within-an-instance which identifies a storage
location for StorageHandle, or a raw subdirectory. Let's use "key".
Change the terminology (and variable names) everywhere.
|
| | |
|
| |
|
|
|
|
| |
Add comments where it's done automatically.
(There will be tests of the claims I'm making, in a later commit.)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This will be slightly less ergonomic at call sites but it is a more
orthogonal and logical API.
|
| |
|
|
|
|
|
| |
Purging depends on the current time.
We will want this to be able to come from Runtime but we don't want to
have those types in this API.
|
| |
|
|
| |
We purge per-kind.
|
| |
|
|
| |
This was probably the result of rebase conflicts during develoopment.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This crate has had new features added. It's 0.x. So bump in-tree
dependencies' references:
fs-mistrust
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bump the minor version of these crates, and update the in-tree
dependencies.
Recently published as fresh crates, let's just assume there are
breaking changes:
fslock-guard
test-temp-dir
Breaking API change affecting many many downstream crates:
tor-rtcompat
Downstream crates which we're (conservatively) assuming have
tor-rtcompat types in their APIs:
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-llcrypto
tor-protover
tor-bytes
tor-hscrypto
tor-hspow
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
tor-congestion
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-bench
arti-testing
|
| |
|
|
| |
Discard hunks in examples/
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
tor-keymgr: Lowercase the role when building the ArtiPath.
Closes #1195
See merge request tpo/core/arti!1934
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
The `slug` docs say slugs are not allowed to contain uppercase
characters, so let's return an error if they do.
Part of #1195
|
| | | |
|
| | |
| |
| |
| | |
This is now InstanceStateHandle::purge.
|
| | |
| |
| |
| |
| | |
We should add more tests for these error representations but we want
to rework these errors so let's not do all that now.
|
| | |
| |
| |
| |
| |
| | |
Apparently we need
https://github.com/dbrgn/tracing-test/pull/17
too.
|