mirrors/arti.git/crates/tor-circmgr, branch arti-v1.1.3mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.32023-03-31T12:30:14ZPatchlevel bumps for crates whose dependencies just changed.2023-03-31T12:30:14ZNick Mathewsonnickm@torproject.org2023-03-31T12:30:14Zurn:sha1:9ef115a7fb21fe7267d1d91ba7babac8e1b7542e
These crates had no changes until just a moment ago. But since
we updated the versions on some of their dependents, they have now
changed themselves. Thus they get patchlevel bumps.
```
tor-rtmock
tor-protover
tor-socksproto
tor-consdiff
tor-chanmgr
tor-dirclient
tor-hsservice
```
Bump crate versions that have breaking changes2023-03-31T12:28:06ZNick Mathewsonnickm@torproject.org2023-03-31T12:28:06Zurn:sha1:e208fb15adb800ae41e472db464f984e9f4a4f5c
These crates have had breaking changes. They are pre-1.0, so they get
a minor bump.
```
tor-basic-utils
tor-config
```
Bump patchlevel on crates with non-breaking changes2023-03-31T12:24:39ZNick Mathewsonnickm@torproject.org2023-03-31T12:24:39Zurn:sha1:a81ab391ae9cc3b48cf08cf1b911f1b4cfa8be76
For these crates, the changes are nontrivial, so we
_do_ bump the versions on which their dependent crates depend.
Fortunately, since they are all pre-1.0, we don't need to
distinguish semver-additions from other changes. (Except for arti,
which _is_ post-1.0, but gets a patchlevel bump anyway.)
These are unstable crates with breaking changes:
```
tor-hscrypto
tor-hsclient
```
These have new or extended APIs:
```
safelog
tor-bytes
tor-cell
tor-linkspec
tor-llcrypto
tor-proto
tor-cert
arti-client
```
These have new unstable APIs or features:
```
tor-netdoc
tor-circmgr (also broke some unstable APIs)
arti (is post-1.0)
```
These have bugfixes only:
```
caret
tor-dirmgr
```
tor-circmgr: Make take_or_launch_stub_circuit future Send2023-03-30T14:46:15ZIan Jacksonijackson@chiark.greenend.org.uk2023-03-30T11:17:38Zurn:sha1:dd493307f973451df7c835460a1abe37ce4583f3
thread_rng() isn't Send. We can fix this by not holding it over an
await point.
Add some missing imports2023-03-28T14:49:45ZIan Jacksonijackson@chiark.greenend.org.uk2023-03-28T13:16:17Zurn:sha1:00e522a91ac1ecd59f48dc97a64319d748f2c482
Now
nailing-cargo +stable clippy -p tor-hsclient --all-features --all-targets
actually works.
squash! Add some missing imports
hspool: simplify loop and add a maximum2023-03-22T16:35:41ZNick Mathewsonnickm@torproject.org2023-03-21T13:34:12Zurn:sha1:dffaf60e4ace19c086e16e2cb72c0726615355ddhspool: Clarify/document more TODO HS items.2023-03-22T16:35:41ZNick Mathewsonnickm@torproject.org2023-03-21T13:28:37Zurn:sha1:bd80125d731b9580e3fd6a1cdab8437fd36170bdcircmgr: Make a separate SupportedCircUsage for HS stuff2023-03-22T16:35:41ZNick Mathewsonnickm@torproject.org2023-03-21T13:04:29Zurn:sha1:19a229155cbcc0fa16e4e03a6c03b8e6a65ae38d
This uncovered a bug: NoUsage wasn't correct for Hs circuits because
of its behavior with channel_usage().
circmgr: Declare builder() unconditionally.2023-03-22T16:35:41ZNick Mathewsonnickm@torproject.org2023-03-16T17:06:18Zurn:sha1:35967ca38d52fb138dd41837df5db8dd93ec1087
(Still, only expose it when experimental-api is enabled.)
hspool: Tweak comments and add more TODOs.2023-03-22T16:35:41ZNick Mathewsonnickm@torproject.org2023-03-16T15:58:02Zurn:sha1:5b3c6b6bb3508df6370b69f627794f71c85d8e32