Topic archive
Runtime & Failure
SikiT English global coverage: PC & Software
-
A five-minute cache made my fixes look like failures
An audit kept reporting seven broken links that no live page contained, because its input list came from a cache with a five-minute lifetime. The same edge also…
-
Your scheduler cannot promise the job ran, so let the job decide
launchd documents that interval firings are dropped when the machine sleeps and coalesced when calendar intervals pile up. Neither mode can tell you the work happened, so the…
-
Three times a measurement was wrong and the system looked fine
An audit reported 148 empty sections that did not exist. A second check counted 100 items when there were 128. A third deleted records it had proved were…
-
When an external write ends ambiguously, query instead of retrying
Two records one second apart with identical content digests. The first write succeeded and the caller could not tell, so it wrote again and the server helpfully renamed…
-
Your agent timeout kills the agent and leaves its grandchildren
A timeout that kills the agent PID, or the PID plus its direct children, leaves anything one level deeper still running. Four measured variants on the same three-level…
-
Why disown and nohup did not keep a backgrounded agent alive
A backgrounded agent CLI dies when its terminal goes away. disown does not stop it, and nohup only helps until something re-arms the handler. Measured on macOS with…
-
Why an idempotency guard let an agent create 122 duplicate uploads
A scheduled agent uploaded the same two images 122 times past a reuse guard built to prevent it. The guard compared filenames, and the server renames colliding uploads,…
-
Exit, Ctrl+C, or taskkill: stop the right Windows command
Learn how to distinguish Cmd.exe, a batch script, and a running console process, choose the least destructive stop control, and verify the target ended.
-
Disconnect a Named Pipe Without a Flush Hang
A Win32 shutdown guide that separates the blocking buffer drain from DisconnectNamedPipe and makes graceful delivery versus bounded discard explicit.
-
How to Stop a Windows Named-Pipe Server from Waiting Forever
A finite Win32 wait-and-cancel path that preserves pending I/O state until Windows reports normal completion, cancellation, or failure.