| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
Done using:
```
cargo set-version --bump minor -p arti
```
|
| |
|
|
|
|
|
|
|
| |
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.37.0
done
|
| |
|
|
|
|
|
|
|
| |
Done using
```
(cd crates/hashx/bench && cargo update)
(cd crates/equix/bench && cargo update)
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
```
|
| |\
| |
| |
| |
| | |
Run fixup-features in preparation for release
See merge request tpo/core/arti!3510
|
| | |
| |
| |
| |
| | |
For some reason `cargo-sort` won't sort it on its own, so I've had to
manually move these around to satisfy the check.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
On nightly, clippy now warns against this and recommends using a `match`
instead.
See https://rust-lang.github.io/rust-clippy/master/index.html#unnecessary_unwrap
|
| | | |
|
| | |
| |
| |
| | |
This silences a new nightly warning.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This silences a new warning on nightly.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This silences a new warning on nightly.
|
| | | |
|
| | | |
|
| |/
|
|
| |
This silences a nightly warning.
|
| |\
| |
| |
| |
| | |
arti-client: Fix typo
See merge request tpo/core/arti!3504
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit moves the "Naming Convention" of the parse2::poc module into
the respective module, as it does not apply to parse2 itself, as
outlined in arti!3462.
With this commit, there remains `NdaSystemTimeDeprecatedSyntax` as the
only type outside poc following this naming schema. However, because it
is more or less already deprecated anyways, there is no real need to
bother with it any further.
|
| |\ \
| | |
| | |
| | |
| | | |
tor-dirserver: Improve database::Timestamp
See merge request tpo/core/arti!3501
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit improves upon the work made in arti!3460, by establishing
the `database::Timestamp` type as a general purpose type for the
handling of timestamp throughout the code base.
It also replaces all previous occurrences of `SystemTime` within
`dirmirror::operation`, which leads to the reduction of code complexity
in one particular function, namely `calculate_sync_timeout`.
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
tor-circmgr: Remove feature-gating from `CircMgrConfig::vanguard_config()`
Closes #2270
See merge request tpo/core/arti!3498
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
tor-netdoc: Rename ItemArgument method to avoid clash with tor_bytes
See merge request tpo/core/arti!3499
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
tor_bytes also has a write_onto method. And types (especially utility
types like `Ignored`) might conceivably implement both!
No need for semver update since this was pub(crate) in the previous release.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This is in the ItemValueParseable derive, so the individual fields are
Arguments, not Items.
|
| | |/ / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
tor-dirserver: Use `saturating-time`
See merge request tpo/core/arti!3460
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit replaces the custom implementation of `SaturatingSystemTime`
with the `saturating-time` crate, additionally adding a new type to the
`database` module called `Timestamp`, in order to have a convenient
wrapper around `ToSql` and `FromSql`.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
arti: Put supported request headers in Tor-Capabilties
Closes #2259
See merge request tpo/core/arti!3473
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is for spec conformance; it is a missing piece of prop365.
Closes #2259.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix some errors in and around making directories for logfiles.
Closes #2240, #2265, and #2266
See merge request tpo/core/arti!3491
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will improve the error message for problems similar to
arti#2240, if they recur.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This should fix the main part of arti#2240.
This is an instance of arti#2267 ("Path::parent has funny behavior")
|
