Chinesezjc 2ad93da755 fix(code-runtime-python): treat an absent start-time reading as reaped, not recycled ...

The PID-reuse guard refused to signal whenever the current reading differed
from the one taken at spawn, including when it was ABSENT. On Linux a reaped
leader has no /proc/<pid>/stat, so every teardown after the leader exited
skipped SIGTERM/SIGKILL while the group it led still held survivors -- the
exact case the process-group teardown exists to reap. Three same-group survivor
tests went red on the coverage lane; they pass on Darwin because the reader
always returns undefined there, leaving the guard inert.

Only a present-and-different reading now blocks the signal. Verified on the
self-hosted Linux box: a reaped leader with live survivors allows the signal, a
pid whose start time differs still blocks it, and a live matching process is
signalled.

2026-08-31 14:30:02 +08:00

..

boot-write-failure.spec.ts

fix(code-runtime-python): seal stray fragments, flush by serialized cost, charge lone surrogates fully

2026-08-31 14:22:37 +08:00

protocol-mirror.e2e.ts

…

protocol.spec.ts

…

residual-detach.spec.ts

…

runtime.spec.ts

fix(code-runtime-python): treat an absent start-time reading as reaped, not recycled

2026-08-31 14:30:02 +08:00