@ai-ecoverse/slicc 1.50.0 → 1.50.2

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 +4 -4
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -355,7 +355,7 @@ Without `--browser`, the first row of the ranking that can host seven is chosen,
355
355
 
356
356
  **What the link offers:** `net` (tcp, resolve), `http`, `ws`, `udp`, and `cdp` with the browser that hosts seven (`seven: true`) and every extra, under the local policy with all of their debugging ports protected, and this machine's other debugging ports too (see [Network policy](#network-policy)); and kernel services on `--kernel-port` (default 80, or a spare port when this user can't have 80; `--no-kernel` turns them off) when seven offers `kernel-in` (see [Kernel services](#kernel-services)); and `ssh` only with `--runner` (see [SSH server](#ssh-server)); and `fs` with each `--mount` folder (see [Host folders](#host-folders)). seven gets full control of every listed browser, the one it runs in too. The `cdp` list (HELLO `browsers`) has only the browser that hosts seven and the extras picked with `--browser` or in the picker; the other browsers discovery found are never offered.
357
357
 
358
- The cdp list follows the browsers: an extra that stops answering is taken off the list (`browser-gone`), and listed again with the same id when it answers on the same endpoint again (`browser-back`).
358
+ The cdp list follows the browsers: an extra that stops answering is taken off the list (`browser-gone`), and listed again with the same id when it answers on the same endpoint again (`browser-back`). An extra that never made the list, because it has no browser session (see [What a browser must offer](#cdp-browser-control)), gets one `browser-gone` with `reason` `no-browser-session` right after the link starts. Plain mode says `seven can't drive <name> through slicc: it has no browser session, so slicc can't watch its tabs or keep seven's origin out of them. It isn't listed for cdp; the rest of the link works` for it, and the dashboard `<name> isn't listed for cdp: it has no browser session`, where an extra that stops answering gets `<name> quit; it is no longer listed for cdp` and `<name> quit`.
359
359
 
360
360
  **Flags.**
361
361
  - `--browser <id>`: an id from `slicc browsers` (an installed id such as `chrome`, or `cdp:<host>:<port>`), or a name, case-insensitively. Repeatable: the first hosts seven, the others are extras. Without it, the best match that can host seven. An endpoint in SLICC six's profile is refused (`<id> is SLICC six's Chrome; only --profile six uses it`).
@@ -396,7 +396,7 @@ The cdp list follows the browsers: an extra that stops answering is taken off th
396
396
  - `foreign-browser`: `browser`, `name`, `profile?`, `cdp`, `openedTab` (`true` when slicc opened the seven tab, `false` when one was open). It follows `attached` when the browser hosting seven is an endpoint slicc didn't launch and the user didn't choose it (see above), and always when it is SLICC six's Chrome, with `profile` `six` or `six:<port>`. The same line goes to stderr.
397
397
  - `linked`: `peer?` (the name in seven's HELLO), `tab?` (the seven tab's origin, never its path or fragment), `caps`, `policy` (the summary).
398
398
  - `link-lost`: `reason?` when slicc or seven closed the link (`slicc is exiting`, `slicc is relinking`, seven's `bye` reason, `replaced by a new offer`), or `message?` for a failure. seven sets the link up again after a reload, and a new `linked` follows.
399
- - `browser-gone`, `browser-back`: `browser`, `name`, `role`. A browser stopped answering and left the cdp list, or answers again and is back on it.
399
+ - `browser-gone`, `browser-back`: `browser`, `name`, `role`. A browser stopped answering and left the cdp list, or answers again and is back on it. A `browser-gone` with `reason` `no-browser-session` is for an extra that was never listed, because it has no browser session.
400
400
  - `browser-slow`: `browser`, `name`, `role`, `elapsed` (seconds). A browser slicc launched hasn't written its `DevToolsActivePort` yet, every 10 s from 10 s on (see [`slicc launch`](#slicc-launch---browser-id---profile-name---url-url---headless---no-seven-flags---json)). The dashboard and plain mode show it as `<name> is still starting (slow disk?), <n> s so far`.
401
401
  - `closed`: `browsers`, the ids slicc closed (always a list). It is the last event of every run that got past choosing its browsers.
402
402
  - `error`: `message`, and `browser?` when closing that browser failed. A setup error ends the run with exit 1.
@@ -536,7 +536,7 @@ slicc attach --cdp <url> [--cdp-extra <url>]... [--origin <origin>]... [--signal
536
536
  `attach` links a seven that is open in a running CDP browser and serves the link until it is interrupted (`SIGINT`, `SIGTERM`), or until stdin closes with `--signal stdio`. Status lines go to stderr, and `SLICC_DEBUG=1` adds diagnostics, pion's included. pion never writes to stderr itself.
537
537
 
538
538
  **Flags.**
539
- - `--cdp`: the browser's endpoint. `http://host:port`, with [a token path](#browsers) if the browser wants one, is looked up through `GET /json/version`, and `ws://…` is used as is. slicc talks to the browser WebSocket only and attaches to the tab with `Target.attachToTarget { flatten: true }`. It names one browser; a second `--cdp` is an error. This browser is also listed for the [`cdp`](#cdp-browser-control) capability, with `seven: true`.
539
+ - `--cdp`: the browser's endpoint. `http://host:port`, with [a token path](#browsers) if the browser wants one, is looked up through `GET /json/version`, and `ws://…` is used as is. As in `slicc browsers`, a trailing `/` and a trailing `/json/version`, `/json/list` or `/json` are ignored, here and on `prompt`, `watch`, `wait` and `abort`. slicc talks to the browser WebSocket only and attaches to the tab with `Target.attachToTarget { flatten: true }`. It names one browser; a second `--cdp` is an error. This browser is also listed for the [`cdp`](#cdp-browser-control) capability, with `seven: true`.
540
540
  - `--cdp-extra`: another browser seven may drive over the link (repeatable), in any form `slicc browsers --cdp` takes. Each must answer when `attach` starts.
541
541
  - `--origin`: also accept seven on this origin (`scheme://host[:port]`), repeatable. `https://<label>.sliccy.ai` is always accepted, except `www`.
542
542
  - `--signal`: `cdp` (default) or `stdio`.
@@ -780,7 +780,7 @@ A page RESET or a closed link kills the jerk it started.
780
780
 
781
781
  Only browsers the user named are listed: the one seven runs in, `--cdp` and `--cdp-extra` for `attach`, the extras picked with `--browser` or in the picker for `slicc`, and `--cdp` for `follow`. A browser discovery found but nobody picked is not.
782
782
 
783
- **What a browser must offer.** The filter below needs the browser to pause requests and to report targets on a session of the node's own, so a `cdp` stream needs `Target.attachToBrowserTarget`, and every page it touches needs `Fetch.enable` to take the node's URL patterns and really pause what matches. When `attach`, `follow` or plain `slicc` adds a browser, the node opens one socket and calls `Target.attachToBrowserTarget`. A `wsOnly` browser is skipped, since that is Chrome's opt-in debugging of a running browser, where a socket can raise a consent dialog for a connection that's already gone, so it opens no socket until a stream does. A browser that answers `-32601` isn't listed: slicc says `seven can't drive this browser through slicc`, or logs it in plain `slicc`, and the link goes on without it, without the `cdp` cap when it was the only one. A socket that fails or doesn't answer within 2 s doesn't count, and the stream decides. A browser that has the session but refuses `Fetch.enable` on a page gets `slicc can't keep seven's origin out of this target` on that page. An acknowledgment has to mean a real pause: measured against a browser that acknowledged `Fetch.enable` without pausing, a script's `location = …` into a protected origin loaded it, and a `Runtime.evaluate` racing the commit read the protected page before the node saw it move.
783
+ **What a browser must offer.** The filter below needs the browser to pause requests and to report targets on a session of the node's own, so a `cdp` stream needs `Target.attachToBrowserTarget`, and every page it touches needs `Fetch.enable` to take the node's URL patterns and really pause what matches. When `attach`, `follow` or plain `slicc` adds a browser, the node opens one socket and calls `Target.attachToBrowserTarget`. A `wsOnly` browser is skipped, since that is Chrome's opt-in debugging of a running browser, where a socket can raise a consent dialog for a connection that's already gone, so it opens no socket until a stream does. A browser that answers `-32601` isn't listed: slicc says `seven can't drive this browser through slicc` (plain `slicc` names the browser, and the dashboard says `<name> isn't listed for cdp`; see [The default](#the-default-slicc)), and the link goes on without it, without the `cdp` cap when it was the only one. A socket that fails or doesn't answer within 2 s doesn't count, and the stream decides. A browser that has the session but refuses `Fetch.enable` on a page gets `slicc can't keep seven's origin out of this target` on that page. An acknowledgment has to mean a real pause: measured against a browser that acknowledged `Fetch.enable` without pausing, a script's `location = …` into a protected origin loaded it, and a `Runtime.evaluate` racing the commit read the protected page before the node saw it move.
784
784
 
785
785
  **HELLO** lists the browsers: `"browsers": [{ "id": "chrome", "name": "Chrome (headless)", "version": "154.0.8037.98", "seven": true }]`. Every entry has all four fields.
786
786
  - `id` is the browser kind, then `-2`, `-3`… for a second or third of the same kind. The kind comes from `/json/version`: `electron` for an Electron user agent, else by product `chrome` (also `HeadlessChrome`, and browsers such as Brave that report `Chrome`), `edge` (`Edg`), `opera` (`OPR`), else the product lower-cased up to a `/` or `(`, else `chromium`. So `Crest (WebKit)` is `crest`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ai-ecoverse/slicc",
3
- "version": "1.50.0",
3
+ "version": "1.50.2",
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.50.0",
22
- "@ai-ecoverse/slicc-darwin-amd64": "1.50.0",
23
- "@ai-ecoverse/slicc-linux-arm64": "1.50.0",
24
- "@ai-ecoverse/slicc-linux-amd64": "1.50.0",
25
- "@ai-ecoverse/slicc-windows-arm64": "1.50.0",
26
- "@ai-ecoverse/slicc-windows-amd64": "1.50.0",
21
+ "@ai-ecoverse/slicc-darwin-arm64": "1.50.2",
22
+ "@ai-ecoverse/slicc-darwin-amd64": "1.50.2",
23
+ "@ai-ecoverse/slicc-linux-arm64": "1.50.2",
24
+ "@ai-ecoverse/slicc-linux-amd64": "1.50.2",
25
+ "@ai-ecoverse/slicc-windows-arm64": "1.50.2",
26
+ "@ai-ecoverse/slicc-windows-amd64": "1.50.2",
27
27
  "@ai-ecoverse/slicc-jerk": "^1.3.9"
28
28
  }
29
29
  }