9 Commits

Include renames

Author	SHA1	Message	Date
Nils Andreas Svee	f2fce2f330	refactor(irtt-client): move cadence into managed runner	2026-10-02 00:31:17 +07:00
Nils Andreas Svee	04291a0b7b	feat(server): allow IRTT_SERVER_NO_DSCP to set --no-dscp flag	2026-09-14 15:33:57 +07:00
Nils Andreas Svee	5dd478e81a	fix(app): bound dynamic stream accounting	2026-09-01 10:36:05 +07:00
Nils Andreas Svee	1ba4f61072	feat(app): add stdin-managed client target sets	2026-09-01 01:50:56 +07:00
Nils Andreas Svee	344533f8b6	feat(app): parse target-level HMAC authentication	2026-09-01 01:49:48 +07:00
Nils Andreas Svee	8602f73728	feat(app): add environment variable support for server configuration ... Enable configuration via IRTT_SERVER_* environment variables to simplify deployments in containerized or orchestrated environments. This adds the clap "env" feature and includes thread-safe tests to verify variable precedence.	2026-08-24 15:47:09 +07:00
Nils Andreas Svee	e9e1ff4218	feat(server): give irtt-server sensible zero-argument defaults ... With no --bind, the server now binds the wildcard IRTT port on both address families ([::]:2112 then 0.0.0.0:2112) instead of requiring an explicit address, on platforms where wildcard reply-source selection is already supported. Any explicit --bind fully replaces the default pair rather than adding to it; repeated explicit binds are unaffected. If one of the two default listeners fails because its address family has no local support on this host at all (IPv6 disabled on an otherwise IPv4-capable host, for example), the server falls back to serving just the surviving family instead of failing outright. Any other failure reason -- the port already in use, permission denied, no safe wildcard reply-source path -- is not a family-support problem and is not silently worked around; startup fails as it would for an explicit --bind. This distinction is made with the new irtt_server::address_family_available, which actually binds the wildcard address of the failed listener's family on an ephemeral port: a bare socket can construct successfully even when every bind for that family fails (Linux administratively disabling IPv6 per-interface leaves AF_INET6 sockets constructible but every bind EADDRNOTAVAIL), so only a real bind attempt is a reliable signal.	2026-08-20 22:17:07 +07:00
Nils Andreas Svee	98e7231ede	fix(app): gate feature-specific formatting helpers ... RUSTFLAGS="-D warnings" cargo check -p irtt-rs --no-default-features --features client (or --features tui) warned on dead code: some format.rs helpers are only called from the client applet, others only from the TUI. Narrowly #[cfg(feature = "...")]-gate each to the applet that actually uses it instead of allowing the warning or introducing a new feature, and split the tests that exercised both groups to match.	2026-08-20 14:57:02 +07:00
Nils Andreas Svee	7bea3dd54e	refactor(app): clarify application and binary roles ... Rename the application Cargo package from irtt-cli to irtt-rs (crates/irtt-cli -> crates/irtt-app), and hard-rename its scriptable client binary from irtt-cli to irtt-client, now that the application also ships a first-class server and the old name reads as an umbrella CLI for both roles. Give each dedicated binary (irtt-client, irtt-tui, irtt-server) its own entry point instead of funneling through the multicall dispatcher's argv0/subcommand logic, so a dedicated binary only links the applet code for the role it implements and always runs that role regardless of the name it's invoked or copied under. irtt-rs remains the feature-selectable multicall dispatcher and is now the only binary that inspects argv0 or subcommands. Move future application releases to the irtt-rs/vX.Y.Z tag namespace (regenerated via `dist generate`), and bump the application package to 0.6.0 as a breaking distribution change. Library crate versions are unaffected.	2026-08-20 11:44:35 +07:00