@mark1russell7/machines 0.3.18 → 0.3.20

package/README.md

@@ -34,6 +34,7 @@ The algebra reads these documents. It gives the closed form of each timer, the f
 | `NODE_HTTP_SERVER` | `node-http-server` | One connection of the `http.Server` of Node 24.21.0 | server | 8 implemented |
 | `NODE_HTTP_AGENT` | `node-http-agent` | One socket of the `http.Agent` of Node 24.21.0 | driver | 9 implemented |
 | `UNDICI_CLIENT` | `undici-client-h1` | The socket of an HTTP/1.1 `Client` of undici 8.12.2 | driver | 8 implemented |
+| `UNDICI_RETRY` | `undici-retry-agent` | One request through a `RetryAgent` of undici 8.12.2 | driver | 7 implemented, 1 normative |
 | `GO_TRANSPORT` | `go-nethttp-transport` | One connection of the `http.Transport` of Go 1.27.2 | driver | 7 implemented |
 | `PROCEDURES_WS_CLIENT` | `procedures-ws-client` | The WebSocket client of `@procedures/client` 0.3.0 | driver | 9 implemented, 1 documented |
 | `PROCEDURES_WS_SERVER` | `procedures-ws-server` | The WebSocket server of `@procedures/client` 0.3.0 | server | 4 implemented |
@@ -59,8 +60,9 @@ The algebra reads these documents. It gives the closed form of each timer, the f
 | `TOXIPROXY_LINK` | `toxiproxy-link` | Toxiproxy 2.12.0 with no toxic: one proxied TCP connection and its close | proxy | 9 implemented |
 | `DOCKER_PROXY_LINK` | `docker-proxy-link` | docker-proxy of Docker Engine 29.1.5: one proxied TCP connection and its close | proxy | 9 implemented |
 | `CADDY_HTTP2` | `caddy-http2` | Caddy 2.11.7 as an HTTP/2 proxy of gRPC: one connection of a client, its idle close, its replies and its stop | proxy | 12 implemented |
+| `NGINX_GRPC` | `nginx-grpc` | nginx 1.29.6 as an HTTP/2 proxy of gRPC: one connection of a client, its idle close, the read timer of a call, and a stopped worker | proxy | 12 implemented, 1 documented |
 
-Twenty-eight documents operate on Linux TCP (`over`). Linux TCP, conntrack, the Sentinel, the replication of mongod, aten and the member of Ra operate on no other document. The `conditions` of each document give the range where it holds, for example a range of kernels.
+Twenty-nine documents operate on Linux TCP (`over`). Seven documents operate on no other document: Linux TCP, conntrack, the Sentinel, the replication of mongod, aten, the member of Ra and the `RetryAgent` of undici. The `RetryAgent` is one request above the sockets of a `Client`. Its timer is the delay of a retry. Each retry can go on a new socket. The `conditions` of each document give the range where it holds, for example a range of kernels.
 
 The package also gives these parts:
 

package/build/index.d.ts

@@ -95,6 +95,29 @@ export declare const NODE_HTTP_SERVER: Machine;
  */
 export declare const UNDICI_CLIENT: Machine;
 //#endregion
+//#region src/http/undici-retry.d.ts
+/**
+ * This document is one request through a `RetryAgent` of undici 8.12.2: the retries of a reply
+ * whose status is retryable, for example 429 or 503. Each fact comes from the published package at
+ * 8.12.2, with the file and the line. The defaults are 5 retries, a backoff from 500 ms with a factor
+ * of 2, a cap of 30 s, and Retry-After read.
+ *
+ * - The delay of a retry is the Retry-After of the reply, capped by `maxTimeout`. A Retry-After
+ *   longer than the cap does not stop the retries: the retry comes early. A reply without
+ *   Retry-After gets the backoff, with no jitter.
+ * - The agent gives up after `maxRetries` retries. The caller then gets `RequestRetryError`, with
+ *   the status of the last reply. Thus the retry window of the caller is the sum of the delays.
+ * - A POST and a PATCH are not retried.
+ * - The delay is a native Node timer. It arms after the parse of the whole reply, thus it comes after
+ *   the last segment by the handling time of the program. No source bounds that time, and this
+ *   document does not hold it. The cells add it from a calibration (`HANDLING` in
+ *   `packages/cells/src/http/race.ts`).
+ *
+ * The plain `Client` and `fetch` of undici, and the `fetch` of Node 24.21.0 (undici 7.29.1), send no
+ * request again for a status. Their retry window is 0.
+ */
+export declare const UNDICI_RETRY: Machine;
+//#endregion
 //#region src/ioredis-sentinel.d.ts
 /**
  * This document is the Sentinel path of ioredis 6.0.0. It tells how ioredis finds the primary of a
@@ -400,6 +423,29 @@ export declare const CADDY_HTTP2: Machine;
  */
 export declare const ENVOY_HTTP2: Machine;
 //#endregion
+//#region src/proxy/nginx.d.ts
+/**
+ * This document is nginx 1.29.6 as an HTTP/2 proxy of gRPC, for one connection of a client. Its
+ * configuration is the one of the harness: one worker (the default), one server of h2c, and `grpc_pass`
+ * to one address with no `upstream {}` block. Each other directive is at its built-in default, not at the
+ * values of the stock nginx.conf (keepalive_timeout 65 and worker_processes auto).
+ *
+ * - With no stream open for 75 s (keepalive_timeout), nginx sends GOAWAY NO_ERROR, then a FIN, and it
+ *   reads and drops the input for at most 30 s (the lingering close). A PING does not reset that timer.
+ * - While a stream is open, the connection of the client has no timer. The only timer of a call is
+ *   grpc_read_timeout (60 s) on the upstream socket, from the send of the request. When it fires before
+ *   the headers of the response, the client gets 504 with no gRPC status, thus UNAVAILABLE. After them,
+ *   RST_STREAM INTERNAL_ERROR. nginx does not retry a call that it sent.
+ * - Each call has its own upstream connection, which ends with the call.
+ * - A stopped worker: the timers that came due during the stop fire at the resume. They read one clock,
+ *   which nginx reads after each wait of epoll_wait. After a stop and a continue, that wait fails with
+ *   EINTR (signal(7)). Then nginx fires its timers before it reads any I/O. Thus a stop longer than
+ *   grpc_read_timeout gives 504, also when the reply of the server waits in the socket.
+ * - SIGQUIT and SIGHUP send GOAWAY NO_ERROR, and the worker waits for each stream. SIGTERM exits with
+ *   no GOAWAY.
+ */
+export declare const NGINX_GRPC: Machine;
+//#endregion
 //#region src/proxy/tcp-proxies.d.ts
 /**
  * This document is one proxied connection of Toxiproxy 2.12.0, with no toxic. Toxiproxy copies TCP, and it