mirrors/arti.git/crates/tor-dirserver/Cargo.toml, branch arti-v1.8.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.8.02025-12-02T11:07:59ZBump all the unstable tor- and arti- crates to 0.37.0.2025-12-02T11:07:59ZGabriela Moldovangabi@torproject.org2025-12-02T10:58:54Zurn:sha1:e7d740eda02e05dd53574b6753cc4b45ab160b58
Done using:
```
for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do
cargo set-version -p $crate 0.37.0
done
dirserver: Run cargo-sort in preparation for release2025-12-01T11:40:46ZGabriela Moldovangabi@torproject.org2025-12-01T11:40:46Zurn:sha1:3bc86e4f06bee2d5fc3d231747094dc949cb0c80Run fixup-features in preparation for release2025-12-01T11:37:17ZGabriela Moldovangabi@torproject.org2025-12-01T11:37:17Zurn:sha1:8f6ce316e35289d68ee585d151870dd9d0949c2dtor-dirserver: Use `saturating-time`2025-11-26T10:27:15ZClara Englercve@cve.cx2025-11-25T17:20:32Zurn:sha1:73a053117033d0d26897a009765915739ba73180
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`.
tor-dirserver: Add SaturatingSystemTime2025-10-30T15:54:27ZClara Englercve@cve.cx2025-10-27T11:21:57Zurn:sha1:61a641e9b4b4932849e8aa212348a808d95a7033
This commit changes various things in the dirmirror operation, namely
the use of a SystemTime wrapper type that provides saturation on both
ends.
tor-dirserver: Make database full sync2025-10-30T15:53:27ZClara Englercve@cve.cx2025-10-20T14:33:31Zurn:sha1:b7dd6d4b7e230975347ec99c1db554498e2ace7e
This commit makes the entire database operations synchronous, thereby
replacing deadpool with r2d2.
The full motivation is outlined in a rustdoc comment at the top of the
`database` module, but it can be summarized to the fact that SQLite is
by design inherently synchronous due to directly interfacing with the
file system.
tor-dirserver: Implement download timeout2025-10-30T15:53:25ZClara Englercve@cve.cx2025-10-01T14:08:02Zurn:sha1:f59efc0b66e0a6e1301f8ef23a98345f78295abc
This commit starts work in the `mirror::operation` module by
implementing the functions for calculating the `Duration` to wait from a
given `SystemTime` until the point in time when the dirmirror should
download new documents from the authorities again.
Also, this commit introduces new error types and internal helper
functions in order to fulfill this purpose better.
tor-dirserver: Outline the `mirror` API2025-10-30T15:53:03ZClara Englercve@cve.cx2025-10-01T09:05:45Zurn:sha1:295a21713c4d8fc44981aeb340da36fe5ad9568d
This commit introduces the `mirror` module which is fairly boilerplate
at the moment. However, everything of it is very well documented using
rustdoc, thereby more or less creating a design document.
maint: bump minor versions of all published crates2025-10-29T19:32:37ZSteven Engleropara@torproject.org2025-10-29T19:32:30Zurn:sha1:7e3bc2af0994706f3597cd14d340736a4d0f03e3
```bash
readarray -t publish < <(cargo metadata --format-version 1 | jq -r '.packages[] | select((.id | startswith("path+file:///")) and (.rust_version != null) and (.publish == null or .publish == true or .publish != [])) | .name')
for package in "${publish[@]}"; do echo "$package:"; cargo set-version --bump minor -p "$package"; done
```
tor-dirserver: bump MSRV from 1.83 to 1.862025-10-21T19:15:21ZhashcatHitman3924-hashcatHitman@gitlab.torproject.org2025-10-21T18:58:28Zurn:sha1:b7b7ec5b89753963d47f458f7a578b3a188864ed
I noticed that when doing `cargo generate-lockfile` in the workspace
root, it was locking dependencies to 1.83 compatible versions. It turns
out tor-dirserver started on MSRV 1.83 after we already bumped to 1.85,
and has been missed in MSRV updates ever since.
I've found no indication it is intentionally getting this special
treatment and am assuming it is a mistake.
Signed-off-by: hashcatHitman <3924-hashcatHitman@gitlab.torproject.org>