legacy client

[ala-mode]

copied from this issue.

Response emits hyper_util::client::legacy::Error on expect

looks to be brought in with hyper and tokio

further up is req_client a Client from reqwest::ClientBuiler::new()

when server is not running

thread 'tokio-runtime-worker' panicked at src/main.rs:303:10: Response to be ok: reqwest::Error { kind: Request, url: "https://zingo-1.decentcloud.net:3953/zebrad", source: hyper_util::client::legacy::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })) }

we have also seen this dns error:
Response to be ok: reqwest::Error { kind: Request, url: "https://zingo-1.decentcloud.net:3953/zebrad", source: hyper_util::client::legacy::Error(Connect, ConnectError("dns error", Custom { kind: Interrupted, error: JoinError::Cancelled(Id(32)) })) }

possible path with bespoke data chunking
https://docs.rs/uhttp_chunked_bytes/latest/uhttp_chunked_bytes/

...

This also seems to appear in zingolib.

about the dns error, @zancas states this is "definitively NOT a network error..."

[ala-mode]

Saw this same error pop up with zingo-infra-testutils::integration client_rpcs::get_lightd_info during testing.

thread 'client_rpcs::get_lightd_info' panicked at ~/zingo/infrastructure/testutils/src/test_fixtures.rs:274:10:
called `Result::unwrap()` on an `Err` value: Status { code: Unknown, message: "client error (Connect)", source: Some(hyper_util::client::legacy::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }))) }