mirrors/arti.git/crates/tor-rtcompat, branch arti-v1.2.0mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.02024-02-05T16:13:29ZBump minor versions2024-02-05T16:13:29ZIan Jacksonijackson@chiark.greenend.org.uk2024-02-05T16:13:29Zurn:sha1:af615d87e20d0984f493dfb8dda7b0654d8d7304
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
rtcompat: Fix a rustdoc link.2024-01-30T18:17:49ZNick Mathewsonnickm@torproject.org2024-01-30T18:17:49Zurn:sha1:8942fecd037a1d6c7c377043d379afda598881e7Upgrade to futures-rustls and rustls 0.22.2024-01-25T14:12:43ZNick Mathewsonnickm@torproject.org2024-01-23T19:37:00Zurn:sha1:91735540559d35bb272d0a5e26e61053d38ebd82
The futures-rustls crate has supplanted the async-rustls crate,
and it requires/embeds rustls 0.22.
Closes #1179.
Patchlevel version bumps in preparation for 1.1.12.2024-01-09T13:11:17ZNick Mathewsonnickm@torproject.org2024-01-09T13:07:43Zurn:sha1:ef150707800e7aba78948f0b5dc5a2dcefaf62b6
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
clippy: consequential rustfmt2024-01-02T15:04:18ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-02T12:49:55Zurn:sha1:1ba7e8a78f21b5e1c26c87d12e7a77ebb3a8949dclippy: Use infallible calls2024-01-02T13:56:22ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-02T12:48:56Zurn:sha1:0ce386a24bd5b0490aee28345f90c7ac956a844d
Resolves clippy complaints about needless fallible conversions.
clippy: Replace many calls to .get(0) with .first()2024-01-02T13:56:08ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-02T12:48:44Zurn:sha1:b9da8cf60618b16c021d3ecf1ec24e2dce56aff5
FTR I don't think agree with clippy on this question, but then I often
don't.
tor-rtcompat: use track-caller for thin wrappers2023-12-18T17:02:12ZJim Newsomejnewsome@torproject.org2023-12-18T17:02:12Zurn:sha1:30c07a6c0b544a55795985ff6451f72818fda1c8
In particular, when the (unstable) tokio tracing feature is enabled,
every tracing line includes the name of where the current task was
created. Without this change, that ends up being the name of
intermediate trait methods like TokioRuntimeHandle::block_on, which is
not very helpful.
Adding the `track_caller` attribute causes the name of the caller of
these methods to be used instead, which is typically more helpful.
IIUC this change is not breaking in terms of semver
https://rustc-dev-guide.rust-lang.org/backend/implicit-caller-location.html.
Bump patchlevel versions in preparation for release2023-12-04T16:33:36ZNick Mathewsonnickm@torproject.org2023-12-04T16:22:58Zurn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890
These crates had backward-compatible changes, and get a patchlevel
bump only:
fs-mistrust
tor-error
tor-config
tor-rtcompat
tor-rtmock
This crate exposes no non-CLI APIs, and gets a patchlevel bump only:
arti
Merge branch 'msrv-bump-1.70' into 'main'2023-11-30T14:40:45ZIan Jacksoniwj@torproject.org2023-11-30T14:40:45Zurn:sha1:7b23daffb5c2e903881c9b2d64a0bccc7b3f698e
Increase our MSRV to 1.70
See merge request tpo/core/arti!1773