running-process 4.0.0__tar.gz → 4.0.2__tar.gz

{running_process-4.0.0 → running_process-4.0.2}/Cargo.lock

@@ -59,7 +59,7 @@ version = "1.1.5"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "40c48f72fd53cd289104fc64099abca73db4166ad86ea0b4341abe65af83dadc"
 dependencies = [
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -70,7 +70,7 @@ checksum = "291e6a250ff86cd4a820112fb8898808a366d8f9f58ce16d1f538353ad55747d"
 dependencies = [
  "anstyle",
  "once_cell_polyfill",
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -226,7 +226,7 @@ dependencies = [
  "libc",
  "option-ext",
  "redox_users",
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -260,7 +260,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "39cab71617ae0d63f51a36d69f866391735b51691dbda63cf6f96d042b63efeb"
 dependencies = [
  "libc",
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -461,7 +461,7 @@ dependencies = [
  "recvmsg",
  "tokio",
  "widestring",
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -632,7 +632,7 @@ checksum = "50b7e5b27aa02a74bac8c3f23f448f8d87ff11f92d3aac1a6ed369ee08cc56c1"
 dependencies = [
  "libc",
  "wasi",
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -668,7 +668,7 @@ version = "0.50.3"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "7957b9740744892f114936ab4a57b3f487491bbeafaf8083688b16841a4240e5"
 dependencies = [
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -1026,7 +1026,7 @@ checksum = "dc897dd8d9e8bd1ed8cdad82b5966c3e0ecae09fb1907d58efaa013543185d0a"
 
 [[package]]
 name = "running-process"
-version = "4.0.0"
+version = "4.0.2"
 dependencies = [
  "anyhow",
  "bytes",
@@ -1053,11 +1053,12 @@ dependencies = [
  "tracing",
  "tracing-subscriber",
  "winapi",
+ "windows-sys 0.59.0",
 ]
 
 [[package]]
 name = "running-process-py"
-version = "4.0.0"
+version = "4.0.2"
 dependencies = [
  "interprocess",
  "libc",
@@ -1102,7 +1103,7 @@ dependencies = [
  "errno",
  "libc",
  "linux-raw-sys",
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -1183,7 +1184,7 @@ checksum = "9eb6ea5562eeaed6936b8b54e086aa0f88b9e5b1bef45beb038e2519fa1185b1"
 dependencies = [
  "cfg-if",
  "libc",
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -1246,7 +1247,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "3a766e1110788c36f4fa1c2b71b387a7815aa65f88ce0229841826633d93723e"
 dependencies = [
  "libc",
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -1297,7 +1298,7 @@ dependencies = [
  "getrandom 0.4.2",
  "once_cell",
  "rustix",
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -1375,7 +1376,7 @@ dependencies = [
  "signal-hook-registry",
  "socket2",
  "tokio-macros",
- "windows-sys",
+ "windows-sys 0.61.2",
 ]
 
 [[package]]
@@ -1663,6 +1664,15 @@ version = "0.2.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "f0805222e57f7521d6a62e36fa9163bc891acd422f971defe97d64e70d0a4fe5"
 
+[[package]]
+name = "windows-sys"
+version = "0.59.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "1e38bc4d79ed67fd075bcc251a1c39b32a1776bbe92e5bef1f0bf1f8c531853b"
+dependencies = [
+ "windows-targets",
+]
+
 [[package]]
 name = "windows-sys"
 version = "0.61.2"

{running_process-4.0.0 → running_process-4.0.2}/Cargo.toml

@@ -3,7 +3,7 @@ resolver = "2"
 members = ["crates/running-process", "crates/running-process-py", "crates/test-watchdog"]
 
 [workspace.package]
-version = "4.0.0"
+version = "4.0.2"
 edition = "2021"
 rust-version = "1.85"
 license = "BSD-3-Clause"

{running_process-4.0.0 → running_process-4.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: running_process
-Version: 4.0.0
+Version: 4.0.2
 License-File: LICENSE
 Summary: A Rust-backed subprocess wrapper with split stdout/stderr streaming
 Home-Page: https://github.com/zackees/running-process
@@ -200,6 +200,11 @@ PTY behavior:
 
 There is also a compatibility alias: `RunningProcess.psuedo_terminal(...)`.
 
+Rust consumers should make the same transport choice explicitly: use
+`NativeProcess` for one-shot noninteractive work and
+`InteractivePtySession` / `NativePtyProcess` only for real terminal sessions.
+See [Rust PTY guidance](docs/RUST_PTY.md).
+
 You can also inspect the intended interactive launch semantics without launching a child:
 
 ```python
@@ -283,7 +288,7 @@ PTY mode is intentionally more conservative:
 ./test
 ```
 
-`./install` bootstraps `rustup` into the shared user locations (`~/.cargo` and `~/.rustup`, or `CARGO_HOME` / `RUSTUP_HOME` if you override them), then installs the exact toolchain pinned in `rust-toolchain.toml`. Toolchain installs are serialized with a lock so concurrent repo bootstraps do not race the same shared version.
+`./install` bootstraps `rustup` into the shared user locations (`~/.cargo` and `~/.rustup`, or `CARGO_HOME` / `RUSTUP_HOME` if you override them), then installs the exact toolchain pinned in `rust-toolchain.toml`. Toolchain installs are serialized with a lock so concurrent repo bootstraps do not race the same shared version. Rust build commands run through `uvx soldr`, so there is no separate `soldr` install step to maintain.
 
 `./lint` applies `cargo fmt` and Ruff autofixes before running the remaining lint checks, so fixable issues are rewritten in place.
 
@@ -291,16 +296,32 @@ PTY mode is intentionally more conservative:
 
 On local developer machines, `./test` also runs the Linux Docker preflight so Windows and macOS development catches Linux wheel, lint, and non-live pytest regressions before push. GitHub-hosted Actions skip that Docker-only preflight and run the native platform suite directly.
 
-If you want to invoke pytest directly, set `RUNNING_PROCESS_LIVE_TESTS=1` and run `uv run pytest -m live`.
+For a live-only test run with the timeout crash watchdog and automatic thread
+dumps still enabled, use:
 
-For direct Rust commands, prefer the repo trampolines, which prepend the shared `rustup` proxy location:
+```bash
+uv run -m ci.test --live-only
+```
+
+For a narrower live-only selection, pass pytest targets and selectors through
+the same entrypoint:
 
 ```bash
-./_cargo check --workspace
-./_cargo fmt --all --check
-./_cargo clippy --workspace --all-targets -- -D warnings
+uv run -m ci.test --live-only tests/test_pty_support.py interrupt
 ```
 
+For direct Cargo build commands, use `uvx soldr` directly:
+
+```bash
+uvx soldr cargo check --workspace
+uvx soldr cargo test --workspace
+uvx soldr cargo package -p running-process --no-verify
+```
+
+Keep `maturin`, `cargo fmt`, and `cargo clippy` on their normal entrypoints.
+This repo's high-level scripts already choose the compatible path for those
+tools.
+
 On Windows, native rebuilds that compile bundled C code should run from a Visual Studio developer shell. When the environment is ambiguous, point `maturin` at the MSVC toolchain binaries directly rather than relying on the generic cargo proxy.
 
 For local extension rebuilds, prefer:

{running_process-4.0.0 → running_process-4.0.2}/README.md

@@ -186,6 +186,11 @@ PTY behavior:
 
 There is also a compatibility alias: `RunningProcess.psuedo_terminal(...)`.
 
+Rust consumers should make the same transport choice explicitly: use
+`NativeProcess` for one-shot noninteractive work and
+`InteractivePtySession` / `NativePtyProcess` only for real terminal sessions.
+See [Rust PTY guidance](docs/RUST_PTY.md).
+
 You can also inspect the intended interactive launch semantics without launching a child:
 
 ```python
@@ -269,7 +274,7 @@ PTY mode is intentionally more conservative:
 ./test
 ```
 
-`./install` bootstraps `rustup` into the shared user locations (`~/.cargo` and `~/.rustup`, or `CARGO_HOME` / `RUSTUP_HOME` if you override them), then installs the exact toolchain pinned in `rust-toolchain.toml`. Toolchain installs are serialized with a lock so concurrent repo bootstraps do not race the same shared version.
+`./install` bootstraps `rustup` into the shared user locations (`~/.cargo` and `~/.rustup`, or `CARGO_HOME` / `RUSTUP_HOME` if you override them), then installs the exact toolchain pinned in `rust-toolchain.toml`. Toolchain installs are serialized with a lock so concurrent repo bootstraps do not race the same shared version. Rust build commands run through `uvx soldr`, so there is no separate `soldr` install step to maintain.
 
 `./lint` applies `cargo fmt` and Ruff autofixes before running the remaining lint checks, so fixable issues are rewritten in place.
 
@@ -277,16 +282,32 @@ PTY mode is intentionally more conservative:
 
 On local developer machines, `./test` also runs the Linux Docker preflight so Windows and macOS development catches Linux wheel, lint, and non-live pytest regressions before push. GitHub-hosted Actions skip that Docker-only preflight and run the native platform suite directly.
 
-If you want to invoke pytest directly, set `RUNNING_PROCESS_LIVE_TESTS=1` and run `uv run pytest -m live`.
+For a live-only test run with the timeout crash watchdog and automatic thread
+dumps still enabled, use:
 
-For direct Rust commands, prefer the repo trampolines, which prepend the shared `rustup` proxy location:
+```bash
+uv run -m ci.test --live-only
+```
+
+For a narrower live-only selection, pass pytest targets and selectors through
+the same entrypoint:
 
 ```bash
-./_cargo check --workspace
-./_cargo fmt --all --check
-./_cargo clippy --workspace --all-targets -- -D warnings
+uv run -m ci.test --live-only tests/test_pty_support.py interrupt
 ```
 
+For direct Cargo build commands, use `uvx soldr` directly:
+
+```bash
+uvx soldr cargo check --workspace
+uvx soldr cargo test --workspace
+uvx soldr cargo package -p running-process --no-verify
+```
+
+Keep `maturin`, `cargo fmt`, and `cargo clippy` on their normal entrypoints.
+This repo's high-level scripts already choose the compatible path for those
+tools.
+
 On Windows, native rebuilds that compile bundled C code should run from a Visual Studio developer shell. When the environment is ambiguous, point `maturin` at the MSVC toolchain binaries directly rather than relying on the generic cargo proxy.
 
 For local extension rebuilds, prefer:

{running_process-4.0.0 → running_process-4.0.2}/crates/running-process/Cargo.toml

@@ -35,13 +35,15 @@ path = "src/bin/trampoline.rs"
 # Final feature scheme per #165:
 # * `core`   — always-available API (spawn / pty / containment).
 # * `client` — adds proto types + IPC client (prost, interprocess, dirs).
-# * `daemon` — superset of client; adds the full daemon runtime
-#              (tokio, rusqlite, tracing, etc.).
+# * `telemetry` — tee sink primitives without the full daemon runtime.
+# * `daemon`    — superset of client; adds the full daemon runtime
+#                 (tokio, rusqlite, tracing, etc.).
 # Default ships `client` so `cargo install running-process` installs
 # the `runpm` binary out of the box (per Q1 resolution in #165:
 # `required-features` are not auto-activated by cargo install).
 default = ["client"]
 core = []
+telemetry = []
 client = ["dep:prost", "dep:prost-types", "dep:interprocess", "dep:dirs", "dep:anyhow", "dep:clap"]
 daemon = [
     "client",
@@ -96,6 +98,25 @@ serde_json = "1"
 tempfile = "3"
 test-watchdog = { path = "../test-watchdog" }
 
+# #150: ConPTY passthrough rewrite uses windows-sys directly for the
+# new conpty_passthrough module. Kept alongside (not replacing) the
+# existing winapi 0.3 dep because the rest of the crate's Windows
+# call sites are on winapi and migrating them is out of scope.
+# windows-sys 0.59 exposes CreatePseudoConsole / ResizePseudoConsole /
+# ClosePseudoConsole + PROC_THREAD_ATTRIBUTE_PSEUDOCONSOLE directly.
+[target.'cfg(windows)'.dependencies]
+windows-sys = { version = "0.59", features = [
+    "Win32_Foundation",
+    "Win32_Security",
+    "Win32_Storage_FileSystem",
+    "Win32_System_Console",
+    "Win32_System_IO",
+    "Win32_System_Memory",
+    "Win32_System_Pipes",
+    "Win32_System_Threading",
+    "Win32_System_Diagnostics_Debug",
+] }
+
 # Wave 5 of #165: extra dev-deps absorbed from `running-process-daemon`
 # for its windows-only and unix-only integration tests.
 [target.'cfg(windows)'.dev-dependencies]

{running_process-4.0.0 → running_process-4.0.2}/crates/running-process/proto/daemon.proto

@@ -63,6 +63,10 @@ enum RequestType {
   REQUEST_TYPE_BULK_TERMINATE_SESSIONS = 73;
   // Resize a PTY session without attaching (#130 M5 follow-up).
   REQUEST_TYPE_RESIZE_PTY_SESSION     = 74;
+  // Optional daemon-owned tee telemetry (#131).
+  REQUEST_TYPE_REGISTER_SESSION_TEE   = 75;
+  REQUEST_TYPE_UNREGISTER_SESSION_TEE = 76;
+  REQUEST_TYPE_GET_SESSION_TEE_STATUS = 77;
 }
 
 enum StatusCode {
@@ -133,6 +137,9 @@ message DaemonRequest {
   PurgeExitedSessionsRequest  purge_exited_sessions  = 72;
   BulkTerminateSessionsRequest bulk_terminate_sessions = 73;
   ResizePtySessionRequest     resize_pty_session     = 74;
+  RegisterSessionTeeRequest   register_session_tee   = 75;
+  UnregisterSessionTeeRequest unregister_session_tee = 76;
+  GetSessionTeeStatusRequest  get_session_tee_status = 77;
 }
 
 message DaemonResponse {
@@ -177,6 +184,9 @@ message DaemonResponse {
   PurgeExitedSessionsResponse  purge_exited_sessions  = 72;
   BulkTerminateSessionsResponse bulk_terminate_sessions = 73;
   ResizePtySessionResponse     resize_pty_session     = 74;
+  RegisterSessionTeeResponse   register_session_tee   = 75;
+  UnregisterSessionTeeResponse unregister_session_tee = 76;
+  GetSessionTeeStatusResponse  get_session_tee_status = 77;
 }
 
 // ---------------------------------------------------------------------------
@@ -763,6 +773,79 @@ message ResizePtySessionRequest {
 }
 message ResizePtySessionResponse {}
 
+// ---------------------------------------------------------------------------
+// Optional session tee telemetry (#131).
+// ---------------------------------------------------------------------------
+
+enum TeeSessionKind {
+  TEE_SESSION_KIND_UNSPECIFIED = 0;
+  TEE_SESSION_KIND_PTY         = 1;
+  TEE_SESSION_KIND_PIPE        = 2;
+}
+
+enum TeeStreamKind {
+  TEE_STREAM_KIND_UNSPECIFIED = 0;
+  TEE_STREAM_KIND_PTY_OUTPUT  = 1;
+  TEE_STREAM_KIND_STDOUT      = 2;
+  TEE_STREAM_KIND_STDERR      = 3;
+  TEE_STREAM_KIND_STDIN       = 4;
+}
+
+enum TeeSinkKind {
+  TEE_SINK_KIND_UNSPECIFIED = 0;
+  // Daemon opens the path and owns the file descriptor until the tee is
+  // removed or the session ends. Path bytes are OS-native, not UTF-8.
+  TEE_SINK_KIND_FILE        = 1;
+}
+
+enum TeeFileMode {
+  TEE_FILE_MODE_APPEND   = 0;
+  TEE_FILE_MODE_TRUNCATE = 1;
+}
+
+enum TeeBackpressure {
+  TEE_BACKPRESSURE_DROP_OLDEST = 0;
+  TEE_BACKPRESSURE_BLOCK       = 1;
+}
+
+message RegisterSessionTeeRequest {
+  string session_id          = 1;
+  TeeSessionKind session_kind = 2;
+  TeeStreamKind stream       = 3;
+  TeeSinkKind sink_kind      = 4;
+  // OS-native path bytes: Unix = OsStr bytes; Windows = little-endian UTF-16.
+  bytes  file_path           = 5;
+  TeeFileMode file_mode      = 6;
+  // 0 means use the daemon default.
+  uint32 queue_capacity      = 7;
+  // false means write missed-byte markers, matching the Rust default.
+  bool   suppress_missed_markers = 8;
+  TeeBackpressure backpressure = 9;
+}
+
+message RegisterSessionTeeResponse {
+  uint64 tee_handle = 1;
+}
+
+message UnregisterSessionTeeRequest {
+  string session_id          = 1;
+  TeeSessionKind session_kind = 2;
+  uint64 tee_handle          = 3;
+}
+message UnregisterSessionTeeResponse {}
+
+message GetSessionTeeStatusRequest {
+  string session_id          = 1;
+  TeeSessionKind session_kind = 2;
+  uint64 tee_handle          = 3;
+}
+
+message GetSessionTeeStatusResponse {
+  TeeStreamKind stream       = 1;
+  uint64 missed_bytes        = 2;
+  bool   disconnected        = 3;
+}
+
 // Daemon -> client stream frame for an attached stdout/stderr.
 message PipeStreamFrame {
   oneof frame {

{running_process-4.0.0 → running_process-4.0.2}/crates/running-process/src/client/client.rs

@@ -778,6 +778,12 @@ pub fn connect_or_start(scope_hash: Option<&str>) -> Result<DaemonClient, Client
     spawn_daemon()?;
 
     // Retry with exponential back-off.
+    //
+    // #199: intentional — the daemon binds its socket asynchronously
+    // after `spawn_daemon()` returns. There's no event the OS can
+    // signal us with when the socket is ready, so we poll. Exponential
+    // back-off (50→100→200→400ms) is the standard pattern; total
+    // wait caps at 750ms.
     let delays_ms: [u64; 4] = [50, 100, 200, 400];
     for delay in delays_ms {
         std::thread::sleep(std::time::Duration::from_millis(delay));

{running_process-4.0.0 → running_process-4.0.2}/crates/running-process/src/client/mod.rs

@@ -5,10 +5,12 @@
 //! previously imported from `running_process_client::*` keeps working
 //! when it switches to `running_process::client::*`.
 
+#[allow(clippy::module_inception)]
 pub mod client;
 pub mod paths;
 pub mod pipe_session;
 pub mod pty_session;
+pub mod telemetry;
 
 pub use client::{
     connect_or_start, daemonize_command, launch_detached, ClientError, DaemonClient,
@@ -16,3 +18,7 @@ pub use client::{
 };
 pub use pipe_session::{PipeSpawnRequest, PipeStreamAttachment, SpawnedPipeSession};
 pub use pty_session::{AttachError, PtyAttachment, PtySpawnRequest, SpawnedPtySession};
+pub use telemetry::{
+    SessionTeeBackpressure, SessionTeeFileMode, SessionTeeFileRequest, SessionTeeKind,
+    SessionTeeStatus, SessionTeeStream,
+};

{running_process-4.0.0 → running_process-4.0.2}/crates/running-process/src/client/pty_session.rs

@@ -370,6 +370,12 @@ impl PtyAttachment {
                 return Ok(None);
             }
             // Sleep a small amount; the OS will buffer incoming data.
+            //
+            // #199: intentional — `interprocess::local_socket::Stream`
+            // lacks a portable peek/ready primitive on Windows. The
+            // 20ms poll is the documented fallback. Replacing with
+            // an event-based primitive would require a per-platform
+            // shim that the upstream crate doesn't expose.
             std::thread::sleep(Duration::from_millis(20));
             // Probe by peeking a single byte: read from reader will block,
             // so we use the BufReader.fill_buf trick by reading 0 bytes