running-process 4.6.3__tar.gz → 4.6.4__tar.gz

{running_process-4.6.3 → running_process-4.6.4}/Cargo.lock

@@ -1351,7 +1351,7 @@ dependencies = [
 
 [[package]]
 name = "running-process"
-version = "4.6.3"
+version = "4.6.4"
 dependencies = [
  "anyhow",
  "blake3",
@@ -1390,7 +1390,7 @@ dependencies = [
 
 [[package]]
 name = "running-process-observer"
-version = "4.6.3"
+version = "4.6.4"
 dependencies = [
  "blake3",
  "dirs",
@@ -1401,21 +1401,21 @@ dependencies = [
 
 [[package]]
 name = "running-process-observer-interposer-linux"
-version = "4.6.3"
+version = "4.6.4"
 dependencies = [
  "libc",
 ]
 
 [[package]]
 name = "running-process-observer-interposer-macos"
-version = "4.6.3"
+version = "4.6.4"
 dependencies = [
  "libc",
 ]
 
 [[package]]
 name = "running-process-observer-interposer-windows"
-version = "4.6.3"
+version = "4.6.4"
 dependencies = [
  "retour",
  "windows-sys 0.59.0",
@@ -1423,7 +1423,7 @@ dependencies = [
 
 [[package]]
 name = "running-process-py"
-version = "4.6.3"
+version = "4.6.4"
 dependencies = [
  "interprocess",
  "libc",
@@ -1437,7 +1437,7 @@ dependencies = [
 
 [[package]]
 name = "running-process-win-gnu-bridge"
-version = "4.6.3"
+version = "4.6.4"
 dependencies = [
  "windows-sys 0.59.0",
 ]

{running_process-4.6.3 → running_process-4.6.4}/Cargo.toml

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

{running_process-4.6.3 → running_process-4.6.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: running_process
-Version: 4.6.3
+Version: 4.6.4
 License-File: LICENSE
 Summary: A Rust-backed subprocess wrapper with split stdout/stderr streaming
 Home-Page: https://github.com/zackees/running-process

{running_process-4.6.3 → running_process-4.6.4}/crates/running-process/tests/daemon_tui_repaint_test.rs

@@ -12,8 +12,18 @@
 //! 0.9.0 doesn't expose the PASSTHROUGH flag and ConPTY would
 //! synthesize a virtual-screen re-emission instead of forwarding the
 //! child's bytes verbatim. With the W3-W5 ConPTY rewrite the bytes
-//! flow through unmodified, so the assertions below pass on all
-//! platforms (Windows, macOS, Linux).
+//! flow through, so the assertions below pass on all platforms
+//! (Windows, macOS, Linux).
+//!
+//! What "passthrough" guarantees (#660): the *payload* survives — the
+//! escape sequences reach the reader instead of being swallowed by a
+//! virtual-screen re-render. It does NOT guarantee byte-for-byte
+//! encoding: ConPTY on current Windows runner images re-emits
+//! `CUP(1,1)` in its canonical short form `\x1b[H` (both parameters
+//! defaulted) rather than the long form `\x1b[1;1H` the child wrote.
+//! The cursor-home assertion below is therefore semantic — it accepts
+//! either encoding. Assertions over library-generated bytes, parser
+//! fixtures, and host-to-child input stay byte-exact.
 
 use running_process::daemon::client::DaemonClient;
 use running_process::daemon::paths;
@@ -25,6 +35,23 @@ use std::path::PathBuf;
 use std::process::Command;
 use std::time::{Duration, Instant};
 
+/// True when `bytes` contains a *tick repaint*: a cursor-home escape
+/// immediately followed by `COUNTER`.
+///
+/// Both encodings the OS may deliver are accepted — the explicit
+/// `CUP(1,1)` the child emits (`\x1b[1;1H`) and ConPTY's canonical
+/// all-defaults form (`\x1b[H`). Deliberately narrow: arbitrary
+/// `CUP(row,col)` is NOT accepted, only the two spellings of "home".
+///
+/// Anchoring on the `COUNTER` payload matters. The testbin's clear
+/// preamble is `\x1b[H\x1b[2J`, so a bare "contains `\x1b[H`" check
+/// would be satisfied by the preamble alone and would no longer prove
+/// the per-tick repaint escapes survived the PTY.
+fn contains_cursor_home_repaint(bytes: &[u8]) -> bool {
+    let has = |needle: &[u8]| bytes.windows(needle.len()).any(|w| w == needle);
+    has(b"\x1b[1;1HCOUNTER") || has(b"\x1b[HCOUNTER")
+}
+
 fn testbin_path(name: &str) -> PathBuf {
     let output = Command::new(env!("CARGO"))
         .args([
@@ -214,17 +241,21 @@ async fn raw_ansi_bytes_flow_through_pty_to_ring_buffer() {
             "expected non-empty backlog from testbin output over 3s"
         );
 
-        // ── Byte-exact ANSI assertions (PASSTHROUGH proof) ──────────────
-        // The clear sequence must appear verbatim.
+        // ── ANSI passthrough assertions ─────────────────────────────────
+        // `\x1b[2J` has no default-parameter short form, so ConPTY has
+        // nothing to canonicalize: it must appear verbatim.
         assert!(
             bytes.windows(4).any(|w| w == b"\x1b[2J"),
             "clear-screen escape `\\x1b[2J` missing from backlog: {:?}",
             String::from_utf8_lossy(&bytes)
         );
-        // The cursor-home escape must appear verbatim too.
+        // Cursor-home is semantic: ConPTY may re-encode the child's
+        // `\x1b[1;1H` as the equivalent `\x1b[H`. Either form proves the
+        // escape survived the PTY instead of being eaten. See #660.
         assert!(
-            bytes.windows(6).any(|w| w == b"\x1b[1;1H"),
-            "cursor-home escape `\\x1b[1;1H` missing from backlog: {:?}",
+            contains_cursor_home_repaint(&bytes),
+            "tick repaint missing from backlog: expected `\\x1b[1;1HCOUNTER` \
+             or its canonical equivalent `\\x1b[HCOUNTER`; got: {:?}",
             String::from_utf8_lossy(&bytes)
         );
 
@@ -244,3 +275,30 @@ async fn raw_ansi_bytes_flow_through_pty_to_ring_buffer() {
     .await
     .expect("client task");
 }
+
+/// Unit coverage for the semantic cursor-home matcher (#660).
+///
+/// The live repaint test above is skipped on hosts without
+/// `PSEUDOCONSOLE_PASSTHROUGH_MODE` (Win10) and never exercises the
+/// ConPTY-canonicalized branch on Unix, so pin the matcher's contract
+/// here — it runs on every platform.
+#[test]
+fn cursor_home_repaint_matcher_accepts_both_encodings() {
+    // The long form the testbin actually writes (Unix, and Windows
+    // when ConPTY forwards verbatim).
+    assert!(contains_cursor_home_repaint(
+        b"\x1b[H\x1b[2J\x1b[1;1HCOUNTER: 0\r\n"
+    ));
+    // ConPTY's canonical all-defaults re-encoding of the same CUP(1,1).
+    assert!(contains_cursor_home_repaint(
+        b"\x1b[H\x1b[2J\x1b[HCOUNTER: 0\r\n"
+    ));
+
+    // The clear preamble alone must NOT satisfy the matcher — this is
+    // the regression that anchoring on `COUNTER` exists to prevent.
+    assert!(!contains_cursor_home_repaint(b"\x1b[H\x1b[2J"));
+    // Nor may the payload appear without a cursor-home escape.
+    assert!(!contains_cursor_home_repaint(b"COUNTER: 0\r\n"));
+    // Arbitrary CUP is not "home".
+    assert!(!contains_cursor_home_repaint(b"\x1b[2;1HCOUNTER: 0"));
+}

{running_process-4.6.3 → running_process-4.6.4}/crates/running-process-py/Cargo.toml

@@ -20,7 +20,7 @@ crate-type = ["cdylib", "lib"]
 libc = "0.2"
 pyo3 = { workspace = true }
 regex = "1"
-running-process = { path = "../running-process", version = "4.6.3", features = ["client", "originator-scan"] }
+running-process = { path = "../running-process", version = "4.6.4", features = ["client", "originator-scan"] }
 sysinfo = "0.30"
 winapi = { version = "0.3", features = ["consoleapi", "handleapi", "jobapi2", "processenv", "processthreadsapi", "synchapi", "winbase", "wincon", "winnt", "winuser"] }
 prost = "0.14"

{running_process-4.6.3 → running_process-4.6.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "soldr"
 
 [project]
 name = "running_process"
-version = "4.6.3"
+version = "4.6.4"
 description = "A Rust-backed subprocess wrapper with split stdout/stderr streaming"
 readme = "README.md"
 requires-python = ">=3.10"

{running_process-4.6.3 → running_process-4.6.4}/src/running_process/__init__.py

@@ -1,6 +1,6 @@
 from __future__ import annotations
 
-__version__ = "4.6.3"
+__version__ = "4.6.4"
 
 from running_process._native import (
     ContainedProcessGroup,