error when connection h3i

[SoufElhabti]

Hello,

new to h3i, I tried to run h3i https://cloudflare-quic.com/
I recieved this error :

 Select an action to queue. `Commit` ends selection and flushes queue. commit
thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/h3i-0.2.0/src/client/sync_client.rs:84:14:
called `Result::unwrap()` on an `Err` value: Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" }
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: h3i::client::sync_client::connect
   4: h3i::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I installed h3i from cargo

[LPardue]

h3i takes a hostname and optional port as documented on https://github.com/cloudflare/quiche/tree/master/h3i#command-line-tool and the tool itself. There is no need for a scheme.

[evanrittenhouse]

@LPardue What if we parse schemes off of the URL and auto-supply it to the :scheme pseudo-header if detected? We could just check the passed host_port for a colon and store it if seen: https://datatracker.ietf.org/doc/html/rfc3986#section-3

[LPardue]

Parsing schemes complicates the tool and documentation for little benefit