@mark1russell7/harness 0.11.7 → 0.11.8

package/image/router/ctwatch.py

@@ -4,9 +4,10 @@
 Each line is {"ev": "ct", "t": <CLOCK_MONOTONIC ns>, "type": "NEW|UPDATE|DESTROY", "state": ...,
 "orig": "src:sport>dst:dport", "reply": "..."}. The stamp is the time that this process read the
 event, which is within a millisecond of the kernel. A listing every PUMP seconds evicts the expired
-entries that it walks past, thus a DESTROY follows an expiry within PUMP plus two listings. A
-listing that takes longer than SLOW seconds writes a "pump-slow" line with its start and its
-length: near it, that bound of the lag does not hold.
+entries that it walks past, thus a DESTROY follows an expiry within PUMP plus two listings, and
+the slack of the sleep and of the read (PUMP_SLACK of the harness, 5 ms). A listing that takes
+longer than SLOW seconds writes a "pump-slow" line with its start and its length: near it, that
+bound of the lag does not hold.
 
   ctwatch.py [--pump SECONDS] [--slow SECONDS]
 """

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package",
   "name": "@mark1russell7/harness",
-  "version": "0.11.7",
+  "version": "0.11.8",
   "description": "A fault-injection harness for connection timers: a cell runs a client against a stock target in Docker, through a topology of routers and proxies, a replicated group under Sentinels or a replica set, injects a fault, measures the kernel's own records and judges a prediction. HTTP clients of Go, Node and undici race the keep-alive of a Node server, and the MongoDB driver meets the faults of a replica set. The WebSocket client of @procedures/client drops a silent connection on its own heartbeat, and the harness times that detection and the reconnect from the program's lines and the kernel's stamps.",
   "keywords": [
     "fault-injection",