@ai-ecoverse/slicc 1.61.14 → 1.61.15

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 +2 -0
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -630,6 +630,7 @@ slicc attach --cdp <url> [--cdp-extra <url>]... [--origin <origin>]... [--signal
630
630
  - A binding call counts only when it comes from that main-frame context and carries its nonce. Calls from iframes, workers, other contexts and other origins, and stale nonces, are ignored.
631
631
  - Each offer starts a new link and replaces the current one.
632
632
  - A navigation or reload ends the link, and the next allowed context starts the setup again with a new nonce.
633
+ - A link that fails on its own while the tab and its context are still there gets a new `hello`, with a new nonce, in that same context, so seven starts a new offer. That covers ICE that fails (as when the network changes under the link), no HELLO within 10 s, a protocol violation, and an offer slicc can't answer. slicc says `link failed (<error>); asking seven to set it up again in <wait>`; the wait starts at 1 s and doubles to 30 s. A link that comes up with the current nonce resets the wait and cancels a `hello` still waiting, so an offer seven repeats during the wait isn't replaced. seven maps the new nonce to the same `local:<node>` link and replaces it; messages with the old nonce are ignored, and so is the failure of a link whose nonce is no longer current, so a superseded link that closes doesn't start another round. A `bye` from seven under the current nonce during the wait cancels the pending `hello` too. A link seven closes itself (its data channels close, as when it unlinks the device) isn't set up again, and neither is one that ends with a `bye`, with slicc exiting or relinking, with a screen-abuse close, or with a navigation, reload, closed or crashed tab, which follow their own rules here. `--signal stdio` doesn't do this; its harness asks for a new `hello` instead.
633
634
  - A closed tab ends the link, and slicc waits for another seven tab.
634
635
  - A tab that closes while slicc attaches to it doesn't stop slicc: each setup call has 10 s, and when the tab is gone slicc looks for another seven tab.
635
636
  - A crashed tab (`Target.targetCrashed`, or `Inspector.targetCrashed` on slicc's session) isn't a closed one: slicc says `seven tab crashed`, ends the link with that reason, and doesn't set up again on the dead page, whose renderer would never answer. It reloads the tab with `Page.reload` (`reloading the seven tab`) and sets up again once the browser reports `Inspector.targetReloadedAfterCrash`, or after 30 s. A tab that is running again by the time slicc looks is set up without a reload. slicc reloads at most 3 times in 5 minutes; after that it says `the seven tab keeps crashing. Reload it and slicc links it again` and waits until someone reloads the tab, closes it, or opens another seven tab, which it then prefers.
@@ -1563,6 +1564,7 @@ Rules:
1563
1564
  - **Hello delivery** is retried until both `globalThis.sliccLinkReceive` and the `sliccLinkSend` binding exist in the main frame's context. The node calls `addBinding` again when the binding is missing (seen on macOS around the about:blank → page swap). The page should also check that `sliccLinkSend` exists before calling it.
1564
1565
  - **On exit** the node sends `bye`.
1565
1566
  - **Navigating or reloading seven drops the link.** The node runs the setup again when a new allowed context appears.
1567
+ - **A link that fails on its own is set up again in the same tab.** When the link ends with an error while the context is still current (ICE failed, no HELLO, a protocol violation, an offer it couldn't answer), the node sends that context a fresh `hello` with a new nonce, after 1 s, doubling to 30 s until a link comes up with the current nonce, which also cancels a pending `hello`. A link the page closes itself (its data channels close) isn't set up again.
1566
1568
  - **A crashed seven tab is reloaded.** On `Target.targetCrashed` or `Inspector.targetCrashed` the node drops the link and reloads the tab with `Page.reload`, at most 3 times in 5 minutes, then runs the setup again once the tab is back. The page gets a fresh `hello` as after any reload.
1567
1569
  - **ICE:** host candidates only. There's no STUN or TURN, since both peers are on the same machine.
1568
1570
  - Chrome hides host candidates behind mDNS (`<uuid>.local`), so the node resolves them (pion `MulticastDNSMode` query-only).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ai-ecoverse/slicc",
3
- "version": "1.61.14",
3
+ "version": "1.61.15",
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.61.14",
22
- "@ai-ecoverse/slicc-darwin-amd64": "1.61.14",
23
- "@ai-ecoverse/slicc-linux-arm64": "1.61.14",
24
- "@ai-ecoverse/slicc-linux-amd64": "1.61.14",
25
- "@ai-ecoverse/slicc-windows-arm64": "1.61.14",
26
- "@ai-ecoverse/slicc-windows-amd64": "1.61.14",
21
+ "@ai-ecoverse/slicc-darwin-arm64": "1.61.15",
22
+ "@ai-ecoverse/slicc-darwin-amd64": "1.61.15",
23
+ "@ai-ecoverse/slicc-linux-arm64": "1.61.15",
24
+ "@ai-ecoverse/slicc-linux-amd64": "1.61.15",
25
+ "@ai-ecoverse/slicc-windows-arm64": "1.61.15",
26
+ "@ai-ecoverse/slicc-windows-amd64": "1.61.15",
27
27
  "@ai-ecoverse/slicc-jerk": "^1.4.2"
28
28
  }
29
29
  }