mirrors/arti.git/crates/tor-netdoc, branch arti-v1.2.8

Bump arti- and tor- crates to 0.23.0

2024-09-30T13:04:32Z

Per our policy, every one of these gets a minor bump. Generated with: ``` for crate in $(./maint/list_crates | grep '^$tor\|arti$-' ); do cargo set-version --bump minor -p $crate; done ``` (Note the use of `-` at the end end of the grep pattern to prevent matching the `arti` crate.)

Merge branch 'msrv-1.77-and-rusqlite-update' into 'main'

2024-09-26T14:24:02Z

Upgrade MSRV to 1.77 , and rusqlite to 0.32.1 See merge request tpo/core/arti!2451

Upgrade MSRV to 1.77

2024-09-26T01:54:22Z

This will allow us to upgrade to the latest version of rusqlite.

Upgrade to derive_more version 1.0.0

2024-09-25T14:37:18Z

The `derive_more` crate broke backward compatibility with this version, so this change involved quite a few manual fixups. With luck, they'll keep compatibility for some while in the future.

Bump MSRV from 1.70 to 1.75.

2024-09-16T21:18:31Z

tor-circmgr: Remove AbstractSpec and FakeSpec.

2024-09-16T14:57:33Z

AbstractSpec and FakeSpec actually make testing more difficult, since they prevent using FakeBuilder in code that relies on the concrete TargetCircUsage and SupportedCircUsage types. Removing them means FakeBuilder can be used in more places, and also means that the test code is closer to the real code, since TargetCircUsage and SupportedCircUsage are now exercised directly in more tests. This did require making one change to a test, which I think was previously testing behaviour that was true for FakeSpec but not for the real code: The mgr::test::isolated test previously asserted that, in the case where three circuits were requested, two with isolation and one without, the non-isolated circuit would be shared with one of the isolated circuits. This was allowed by the FakeSpec::supports function. However, in the actual code, the path is as follows: * AbstractCircMgr::get_or_launch * AbstractCircMgr::prepare_action * CircList::find_open * AbstractSpec::find_supported * abstract_spec_find_supported * OpenEntry::supports * SupportedCircUsage::supports * StreamIsolation::compatible_same_type StreamIsolation::compatible_same_type checks owner_type, which is always zero for non-isolated streams and always non-zero for isolated streams, meaning that a isolated stream will never be compatible with a non-isolated stream. The seems like desirable behaviour, so I simply modified the test to make four connections, two isolated and two not, and checked that the isolated streams never share any circuits, and that the two non-isolated streams use the same circuit. As far as I can tell, this is the intended behaviour in the existing code.

tor-netdoc: impl `Extend` on `NetParams`

2024-09-03T22:23:08Z

Bump all the unstable tor- and arti- crates to 0.22.0.

2024-09-03T17:57:12Z

Done using: ``` for crate in $(./maint/list_crates | rg '^(tor|arti-)'); do cargo set-version -p $crate 0.22.0 done ```

Resolve unreachable_patterns warnings from nightly.

2024-08-13T13:30:42Z

Nightly rust doesn't like it when you have a `match` arm that can never be reached because of an uninhabited type. As such, we can't say stuff like: ``` let x: Option = ...; match x { Some(_) => unreachable!(), None => ... } ```

Don't need to tell docs.rs to enable `docsrs` cfg

2024-08-02T15:11:20Z

It now does it automatically, see .