@ai-ecoverse/slicc 1.49.23 → 1.49.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.
Files changed (2) hide show
  1. package/README.md +1 -1
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -819,7 +819,7 @@ Only browsers the user named are listed: the one seven runs in, `--cdp` and `--c
819
819
  - **Progress** for a target whose setup is under way is the answer to the node's attach to it, or any answer or event on the node's own guard session for that target. Answers and events on the page's sessions, and on other targets, don't count, so a guard that stays silent fails at the 30 s bound even while the browser and the page stay busy. The node checks the bounds every quarter of the shorter one (7.5 s by default).
820
820
  - **Idle bound:** a setup with no progress for 30 s fails, within one check of it (37.5 s). Only time the node spends waiting on the browser's socket counts toward the 30 s. The node reads the browser's messages one at a time and passes each on before it reads the next, so a page that is slow to credit its window stops the reads, and the guard's answers wait unread behind the page's messages. That time doesn't count, for setups and unknown sessions alike, and a stop over 2 s is logged under `SLICC_DEBUG`. The outer bound still counts it.
821
821
  - **Outer bound:** a setup still under way 5 min after it started fails, whatever its progress.
822
- - **Refusals:** when a setup call fails, the node's session is lost or the target closes, the waiting commands, and any after them, are refused at once with `slicc: refused: slicc can't keep seven's origin out of this target`. When a bound fires, the message names it: `…: its guard made no progress in 30s` or `…: its guard wasn't ready in 5m0s`.
822
+ - **Refusals:** When a setup call fails, the node's session is lost or the target closes, both the navigation guard and any pending document confirmation fail immediately; the waiting commands, and any after them, are refused at once with `slicc: refused: slicc can't keep seven's origin out of this target`. An inherited document whose opener or parent was never confirmed stays refused with `…: inherited document has an unknown opener or parent; slicc never confirmed it`; if that opener or parent closed, the reason is `…: inherited document has a gone opener or parent`. An in-process opener frame must map to its owning target through the node's frame or execution-context bookkeeping, and that target's guard must have finished successfully without protected history. The owning target must also have no protected frames or exhausted world tracking, and must still expose a live ordinary default execution context for that opener frame when confirmation decides. A protected or ordinary opener whose context has disappeared stays refused; unknown frame ownership stays refused. When a bound fires, the message names it: `…: its guard made no progress in 30s` or `…: its guard wasn't ready in 5m0s`.
823
823
  - **Caps:** more than 4096 waiting commands, or 64 MiB of them, on one stream reset it with `ENOBUFS`.
824
824
  - **Sessions the node doesn't know.** A page command with a `sessionId` the node hasn't seen on this stream is never forwarded as it stands. The node knows a session from a `Target.attachedToTarget` it relayed or held, from the answer to the page's `Target.attachToTarget` (for a target it knows) or `Target.attachToBrowserTarget`, and from its own sessions. Commands on an unknown session wait, in order, until the session appears, then any guard setup on its target, and are then decided as usual. So a browser that answers an attach before it announces the session can't open a gap.
825
825
  - **Progress** for an unknown session is only a message from the browser on that session id. The browser answering other commands doesn't count, because it says nothing about this session. The bounds are a target's setup bounds (30 s idle, 5 min outer, checked every quarter of the shorter), and so are the caps.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ai-ecoverse/slicc",
3
- "version": "1.49.23",
3
+ "version": "1.49.24",
4
4
  "description": "SLICC's command line for seven: links a machine's network, compute and browsers to seven over WebRTC",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -18,12 +18,12 @@
18
18
  "node": ">=18"
19
19
  },
20
20
  "optionalDependencies": {
21
- "@ai-ecoverse/slicc-darwin-arm64": "1.49.23",
22
- "@ai-ecoverse/slicc-darwin-amd64": "1.49.23",
23
- "@ai-ecoverse/slicc-linux-arm64": "1.49.23",
24
- "@ai-ecoverse/slicc-linux-amd64": "1.49.23",
25
- "@ai-ecoverse/slicc-windows-arm64": "1.49.23",
26
- "@ai-ecoverse/slicc-windows-amd64": "1.49.23",
21
+ "@ai-ecoverse/slicc-darwin-arm64": "1.49.24",
22
+ "@ai-ecoverse/slicc-darwin-amd64": "1.49.24",
23
+ "@ai-ecoverse/slicc-linux-arm64": "1.49.24",
24
+ "@ai-ecoverse/slicc-linux-amd64": "1.49.24",
25
+ "@ai-ecoverse/slicc-windows-arm64": "1.49.24",
26
+ "@ai-ecoverse/slicc-windows-amd64": "1.49.24",
27
27
  "@ai-ecoverse/slicc-jerk": "^1.3.0"
28
28
  }
29
29
  }