@mark1russell7/machines 0.3.22 → 0.3.24

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -25,7 +25,7 @@ The algebra reads these documents. It gives the closed form of each timer, the f
25
25
 
26
26
  | Export | Identifier | System and version | Layer | Sources, by rung |
27
27
  | --- | --- | --- | --- | --- |
28
- | `LINUX_TCP` | `linux-tcp` | TCP of Linux 6.6, for kernels from 6.6 to 6.9 | kernel | 4 normative, 7 implemented |
28
+ | `LINUX_TCP` | `linux-tcp` | TCP of Linux 6.6, for kernels from 6.6 to 6.9 | kernel | 4 normative, 8 implemented |
29
29
  | `NF_CONNTRACK_TCP` | `nf-conntrack-tcp` | The TCP state machine of conntrack on Linux 6.6.87.2 | middlebox | 4 implemented |
30
30
  | `REDIS_CLIENT` | `redis-client` | One client connection of the Redis 8.10.2 server | server | 3 implemented, 1 documented |
31
31
  | `IOREDIS_STATUS` | `ioredis-status` | The connection status of ioredis 6.0.0, standalone | driver | 5 implemented |
@@ -36,8 +36,8 @@ The algebra reads these documents. It gives the closed form of each timer, the f
36
36
  | `UNDICI_CLIENT` | `undici-client-h1` | The socket of an HTTP/1.1 `Client` of undici 8.12.2 | driver | 8 implemented |
37
37
  | `UNDICI_RETRY` | `undici-retry-agent` | One request through a `RetryAgent` of undici 8.12.2 | driver | 7 implemented, 1 normative |
38
38
  | `GO_TRANSPORT` | `go-nethttp-transport` | One connection of the `http.Transport` of Go 1.27.2 | driver | 7 implemented |
39
- | `PROCEDURES_WS_CLIENT` | `procedures-ws-client` | The WebSocket client of `@procedures/client` 0.3.0 | driver | 9 implemented, 1 documented |
40
- | `PROCEDURES_WS_SERVER` | `procedures-ws-server` | The WebSocket server of `@procedures/client` 0.3.0 | server | 4 implemented |
39
+ | `PROCEDURES_WS_CLIENT` | `procedures-ws-client` | The WebSocket client of `@procedures/client` 0.22.0 (client 2408cea) | driver | 9 implemented, 1 documented |
40
+ | `PROCEDURES_WS_SERVER` | `procedures-ws-server` | The WebSocket server of `@procedures/client` 0.22.0 (client 2408cea) | server | 4 implemented |
41
41
  | `MONGODB_NODE` | `mongodb-node` | The MongoDB Node driver 7.7.0, for one server of a replica set | driver | 19 implemented |
42
42
  | `MONGOD_REPL` | `mongod-replication` | The replication of mongod 9.0.4: one member of a replica set | server | 29 implemented |
43
43
  | `MONGOD_SESSION` | `mongod-session` | One client connection of mongod 9.0.4 | server | 6 implemented |
@@ -109,6 +109,12 @@ A change to the version of a system changes its sources too. Each fact of the do
109
109
 
110
110
  In this repository, a snapshot of the predictions of the cells (`packages/cells/src/__snapshots__/predictions.json`) shows each prediction that a change to a document moves.
111
111
 
112
+ ### 0.3.24
113
+
114
+ - **The SYN timer of Linux TCP** (`syn_retransmit`). It is a backoff timer: each firing sends the SYN again. The waits 0 to `tcp_syn_linear_timeouts` are 1 s, and then each wait doubles up to `TCP_RTO_MAX`. The source is `tcp_retransmit_timer` in `net/ipv4/tcp_timer.c` of 6.6, and 6.17 has the same waits. At HZ 1000 a wait of 1 s is up to 64 ms late. The models are `linux.syn-wait` and `linux.syn-wait-lateness` of the algebra 0.7.3.
115
+ - `recovery` over this timer gives the first SYN after a stall. Kind run 40123580623 measured it: a SYN to a pod that was gone stalled until IPVS dropped the pod.
116
+ - One prediction of the snapshot moves, the kind cell T07.defaults.12.
117
+
112
118
  ### 0.3.18
113
119
 
114
120
  - **Caddy 2.11.7 as a proxy of gRPC** (`caddy-http2`), from the source at its tag and of golang.org/x/net v0.59.0. With no stream open for 5 min, Caddy sends GOAWAY NO_ERROR, and it closes the connection 1 s later. A PING of the client does not reset that timer. A failure of the upstream before the headers of a response gives 502, thus UNAVAILABLE. Caddy retries no call at the defaults, and at SIGTERM it waits for each stream.
package/build/index.d.ts CHANGED
@@ -368,10 +368,11 @@ export declare const SUPAVISOR_SERVER: Machine;
368
368
  //#endregion
369
369
  //#region src/procedures-ws.d.ts
370
370
  /**
371
- * This document is the connection of the WebSocket client of `@procedures/client` 0.3.0
372
- * (`WebSocketTransport`), over its socket class and its Linux TCP socket.
371
+ * This document is the connection of the WebSocket client of `@procedures/client` 0.22.0 at
372
+ * commit 2408cea (`WebSocketTransport`), over its socket class and its Linux TCP socket. The
373
+ * root entry uses the global `WebSocket` of Node, and `@procedures/client/node` uses the `ws` package.
373
374
  *
374
- * - The heartbeat is `heartbeat()` of `@mark1russell7/service` 0.4.0. A tick each interval sends a
375
+ * - The heartbeat is `heartbeat()` of `@mark1russell7/service` 0.5.8. A tick each interval sends a
375
376
  * ping only when no pong is awaited. The timeout of the ping starts before its send. A
376
377
  * ping without a pong at its timeout is a miss, and `misses` misses in sequence drop the
377
378
  * connection. With a timeout below the interval, each tick after a miss sends the next ping.
@@ -386,8 +387,9 @@ export declare const SUPAVISOR_SERVER: Machine;
386
387
  */
387
388
  export declare const PROCEDURES_WS_CLIENT: Machine;
388
389
  /**
389
- * This document is one connection as the WebSocket server of `@procedures/client` 0.3.0 holds it
390
- * (`WebSocketServerTransport` on the `ws` package), over its Linux TCP socket.
390
+ * This document is one connection as the WebSocket server of `@procedures/client` 0.22.0 at
391
+ * commit 2408cea holds it (`WebSocketServerTransport` of `@procedures/client/node`, on the `ws`
392
+ * package), over its Linux TCP socket.
391
393
  *
392
394
  * The heartbeat of the server (roadmap R3) is a `setInterval`. Each beat pings each connection,
393
395
  * and the server ends a connection after `misses` beats without a pong (`terminate()`). Thus the