|
4 | 4 | //! builds), this command runs an ordered sequence of subprocess steps followed by |
5 | 5 | //! a readiness poll before the frontend fires the relay WebSocket reconnect. |
6 | 6 | //! |
7 | | -//! OSS builds (env var unset) get a pure no-op — zero WARP knowledge compiled in. |
| 7 | +//! OSS builds (env var unset) get a pure no-op — zero VPN-specific knowledge compiled in. |
8 | 8 |
|
9 | 9 | // Single source of truth for the config schema, shared with build.rs via |
10 | 10 | // `include!`. See reconnect_hook_config.rs for why this is shared, not a module. |
@@ -43,14 +43,14 @@ pub async fn relay_reconnect_hook() -> Result<(), String> { |
43 | 43 | /// Run a fixed-argv command (`argv[0]` + `argv[1..]`) with a wall-clock cap. |
44 | 44 | /// |
45 | 45 | /// `std::process::Command::output()` blocks until the child exits — a wedged |
46 | | -/// `warp-cli` (the exact degraded-transport case this hook targets) would hang |
| 46 | +/// VPN CLI (the exact degraded-transport case this hook targets) would hang |
47 | 47 | /// forever, pinning the blocking-pool thread and leaving the frontend `invoke` |
48 | 48 | /// unresolved. So we spawn, poll `try_wait()` every 500ms, and kill+reap on the |
49 | 49 | /// deadline. Modeled on `media_transcode.rs` `run_ffmpeg_with_timeout`. |
50 | 50 | /// |
51 | 51 | /// stdout/stderr are piped and read only after the child exits. The pipe-buffer |
52 | 52 | /// deadlock noted there (a child blocking on write() when the ~64 KiB OS pipe |
53 | | -/// fills) does not apply: `warp-cli` emits a few lines, far below the buffer. |
| 53 | +/// fills) does not apply: these CLIs emit a few lines, far below the buffer. |
54 | 54 | fn run_with_timeout( |
55 | 55 | argv: &[String], |
56 | 56 | timeout: std::time::Duration, |
|
0 commit comments