mirrors/arti.git/crates/arti/src, branch arti-v1.1.1

Allow clippy::unchecked_duration_subtraction in tests

2023-01-27T13:28:02Z

This panics on error, and we're fine with a panic on misbehavior in tests.

Disable clippy::unlinlined-format-args

2023-01-27T13:27:47Z

This warning kind of snuck up on us! (See #748) For now, let's disable it. (I've cleaned it up in a couple of examples, since those are meant to be more idiomatic and user-facing.) Closes #748.

resolve ip through socks by parsing them

2023-01-03T16:53:16Z

arti: transports parsing: Record this as a ticket

2022-11-30T15:56:16Z

arti, arti-client: Conditionalise various things on pt-client

2022-11-29T16:32:14Z

arti cfg tests: Add some more debug output

2022-11-29T16:32:14Z

bridge non-support: Test that we reject configs

2022-11-21T16:46:19Z

bridge non-support: De-cfg the primary bridge config fields

2022-11-21T16:46:19Z

We now parse the `bridges.enabled` BoolOrAuto, and the `bridges.bridges` list. The `bridges.bridges` list is Vec<()> in the builder, and Vec in the built config. Ie, it is simply a count, and vanishes in the built config. But this count triggers us to try to call build(), to try to parse bridges, and to try to set and honour the enablement boolean. The result is that the type system now ensures that if bridges are disabled, but specified (either by listing them in the config, or writing `enabled=true`), we inevitably try to insist that we have a non-empty Vec, which is of course impossible. There will be a test case too for those who think this too abstract a way to guarantee this property :-).

arti cfg test: Break out expect_err_contains function

2022-11-21T16:46:19Z

Maybe this will want to be in tor-error or something but put it here for now.

bridge non-support: Disable the test for now

2022-11-21T16:46:19Z

This test will start to fail if you compile without bridge support, because we'll start rejecting the test configurations with bridges specified. We'll add a proper test for this later.