@mark1russell7/harness 0.12.2 → 0.12.4

package/image/amqp/client-cluster.mjs

@@ -109,6 +109,9 @@ const open = async () => {
     channel = await connection.createConfirmChannel();
   } catch (error) {
     emit("channel", { event: "open-failed", at: node, failure: failure(error) });
+    // The next open replaces the connection, thus this one ends here and stays out of the next records.
+    connection.close().catch(() => undefined);
+    connection = null;
     return false;
   }
   channel.on("error", (error) => emit("channel", { event: "error", at: node, failure: failure(error) }));

package/image/router/resetter.py

@@ -39,6 +39,9 @@ def sniff(ifname):
         sport, dport, _seq, ack = struct.unpack("!HHII", tcp[:12])
         fl = tcp[13]
         with flock:
+            # A SYN starts a new flow: a 4-tuple that comes again has none of the state of its last flow.
+            if fl & 0x02:
+                flows.pop((src, sport, dst, dport), None)
             f = flows.setdefault((src, sport, dst, dport), {"ack": None, "closed": False})
             if fl & 0x10:
                 f["ack"] = ack
@@ -85,8 +88,10 @@ def main():
         c, s, cp, sp, s2, r, sp2, rp = m.groups()
         cp, sp, sp2, rp = int(cp), int(sp), int(sp2), int(rp)
         k_cs, k_sr = (c, cp, s, sp), (s2, sp2, r, rp)
+        keys = (k_cs, (s, sp, c, cp), (r, rp, s2, sp2), k_sr)
         with flock:
-            fs = {k: dict(flows[k]) for k in (k_cs, (s, sp, c, cp), (r, rp, s2, sp2), k_sr) if k in flows}
+            # Conntrack forgot the flow, thus the table forgets it too.
+            fs = {k: flows.pop(k) for k in keys if k in flows}
         if not fs or any(f["closed"] for f in fs.values()):
             continue
         seq_c = fs.get(k_cs, {}).get("ack")  # the RCV.NXT of the client

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package",
   "name": "@mark1russell7/harness",
-  "version": "0.12.2",
+  "version": "0.12.4",
   "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",