@camstack/addon-osd-manager 0.1.32 → 0.1.34

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/dist/_stub.js CHANGED
@@ -1,5 +1,5 @@
1
1
  import "./virtualExposes-BgZ5Cn7S.mjs";
2
- import "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-CmYtdZEf.mjs";
2
+ import "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-BF_XPbUY.mjs";
3
3
  import { _ as e, c as t, d as n, h as r, i, l as a, m as o, n as s, p as c, r as l, t as u, u as d, y as f } from "./_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare__react__loadShare__.js-Bs1t18EM.mjs";
4
4
  import { i as p, o as m, r as h, s as g } from "./responsive-pP5vcFcr.mjs";
5
5
  import { c as _, l as v, u as y } from "./use-device-snapshot-BQ24djI3.mjs";
@@ -1,9 +1,9 @@
1
- import "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-CmYtdZEf.mjs";
1
+ import "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-BF_XPbUY.mjs";
2
2
  //#region \0virtual:mf-localSharedImportMap:__mfe_internal__addon_osd_manager_page
3
3
  var e = {
4
4
  "@camstack/sdk": {
5
5
  name: "@camstack/sdk",
6
- version: "1.2.42",
6
+ version: "1.2.44",
7
7
  scope: ["default"],
8
8
  loaded: !1,
9
9
  from: "addon_osd_manager_page",
@@ -18,7 +18,7 @@ var e = {
18
18
  },
19
19
  "@camstack/types": {
20
20
  name: "@camstack/types",
21
- version: "1.2.120",
21
+ version: "1.2.122",
22
22
  scope: ["default"],
23
23
  loaded: !1,
24
24
  from: "addon_osd_manager_page",
@@ -33,7 +33,7 @@ var e = {
33
33
  },
34
34
  "@camstack/ui-library": {
35
35
  name: "@camstack/ui-library",
36
- version: "1.2.83",
36
+ version: "1.2.85",
37
37
  scope: ["default"],
38
38
  loaded: !1,
39
39
  from: "addon_osd_manager_page",
@@ -36,7 +36,7 @@ async function r() {
36
36
  }
37
37
  },
38
38
  "@camstack/types": {
39
- version: "1.2.120",
39
+ version: "1.2.122",
40
40
  scope: "default",
41
41
  shareConfig: {
42
42
  singleton: !0,
@@ -45,7 +45,7 @@ async function r() {
45
45
  }
46
46
  },
47
47
  "@camstack/sdk": {
48
- version: "1.2.42",
48
+ version: "1.2.44",
49
49
  scope: "default",
50
50
  shareConfig: {
51
51
  singleton: !0,
@@ -81,7 +81,7 @@ async function r() {
81
81
  }
82
82
  },
83
83
  "@camstack/ui-library": {
84
- version: "1.2.83",
84
+ version: "1.2.85",
85
85
  scope: "default",
86
86
  shareConfig: {
87
87
  singleton: !0,
package/dist/index.js CHANGED
@@ -15579,6 +15579,50 @@ var NodeProcessSchema = object({
15579
15579
  /** Wall-clock uptime (seconds). Parsed from `ps etime`. */
15580
15580
  uptimeSec: number()
15581
15581
  });
15582
+ /**
15583
+ * One retained container-memory reading.
15584
+ *
15585
+ * `atMs` is the timestamp of the PROCESS snapshot taken in the same tick, not
15586
+ * a second clock: that is what makes "processes sum to X, container says Y"
15587
+ * subtractable per point rather than an eyeballed comparison of two series
15588
+ * sampled at different instants.
15589
+ *
15590
+ * A reduced window keeps the sample with the LARGEST `currentBytes` in each
15591
+ * bucket, WHOLE. Taking a per-field maximum would synthesise a row whose parts
15592
+ * never coexisted, and a mean would smear away the peak this exists to find.
15593
+ */
15594
+ var ContainerMemoryPointSchema = object({
15595
+ /** Which hierarchy answered, so a reading is never ambiguous. */
15596
+ source: _enum(["cgroup-v2", "cgroup-v1"]),
15597
+ /** `memory.current` (v2) / `memory.usage_in_bytes` (v1). Always known. */
15598
+ currentBytes: number(),
15599
+ /** The cgroup's ceiling. `null` = NO LIMIT — never a sentinel, never zero. */
15600
+ limitBytes: number().nullable(),
15601
+ /** Anonymous pages: the closest thing to "what the processes allocated". */
15602
+ anonBytes: number().nullable(),
15603
+ /** Page cache. Charged to the cgroup, owned by no process. */
15604
+ fileBytes: number().nullable(),
15605
+ /**
15606
+ * Shared memory — and the field that explained the largest single surprise.
15607
+ * The i915 driver backs GPU buffers with shmem, so an inference pool or a
15608
+ * hardware-decode session holding DRM objects is charged HERE and appears
15609
+ * nowhere in a `ps` scan.
15610
+ */
15611
+ shmemBytes: number().nullable(),
15612
+ /** Kernel slab charged to this cgroup. `null` on v1, which never publishes it. */
15613
+ slabBytes: number().nullable(),
15614
+ /**
15615
+ * Shrinkable i915 GEM object bytes, from debugfs.
15616
+ *
15617
+ * **Host-wide across every DRM client, NOT cgroup-scoped.** It is not a
15618
+ * component of `currentBytes` and must not be subtracted from it; it says
15619
+ * what put the shmem there, where `shmemBytes` only says how much.
15620
+ *
15621
+ * `null` wherever debugfs is not mounted — which is inside every camstack
15622
+ * container today — and on any node with no Intel GPU.
15623
+ */
15624
+ gpuShmemBytes: number().nullable()
15625
+ }).extend({ atMs: number() });
15582
15626
  var DumpHeapSnapshotInputSchema = object({
15583
15627
  /** The addon whose runner should dump a heap snapshot. */
15584
15628
  addonId: string() });
@@ -15642,6 +15686,21 @@ var NodeLoadSeriesSchema = object({
15642
15686
  /** One entry per function seen in the window, heaviest-first. */
15643
15687
  series: array(LoadFunctionSeriesSchema).readonly(),
15644
15688
  /**
15689
+ * The CONTAINER's memory over the same window, oldest-first.
15690
+ *
15691
+ * Sits next to `series` rather than in a method of its own because the whole
15692
+ * question is a subtraction: the per-process rows in `series` sum to one
15693
+ * number and this one is another, and an operator who has to issue two calls
15694
+ * to compare them will compare two different instants. Same reader, same
15695
+ * `sinceMs`, same `bucketMs`, same timestamps.
15696
+ *
15697
+ * **EMPTY means ABSENT, never zero.** A node with no cgroup — a developer
15698
+ * Mac, a bare-metal host, a container with the hierarchy hidden — reports no
15699
+ * points at all. A zero here would be indistinguishable from a healthy
15700
+ * container and is precisely the lie this field exists to avoid.
15701
+ */
15702
+ containerMemory: array(ContainerMemoryPointSchema).readonly(),
15703
+ /**
15645
15704
  * Width of one returned bucket, in ms. Equals the sampling cadence when no
15646
15705
  * reduction was needed — so a caller can always say what one point covers
15647
15706
  * without having to know whether it was reduced.
@@ -32451,10 +32510,10 @@ var rebootCapability = {
32451
32510
  * recording config. NOTE on events (source of truth, R5/C3): this cap carries
32452
32511
  * NO event surface — `getPlaybackManifest` returns playlist URLs only. Timeline
32453
32512
  * events (motion/object/audio) come from `pipelineAnalytics` (durable SQLite
32454
- * rows); the recorder's internal EventMap markers are ephemeral in-RAM
32455
- * annotations that are not exposed here and must not be treated as an event
32456
- * feed. Event<->footage joins are by time, padded with the shared `EVENT_PAD_MS`
32457
- * (`interfaces/recording-config.ts`).
32513
+ * rows) and are the ONLY event surface the recorder has none. The in-RAM
32514
+ * playback markers it used to build were deleted on 2026-08-29 because nothing
32515
+ * ever read them. Event<->footage joins are by time, padded with the shared
32516
+ * `EVENT_PAD_MS` (`interfaces/recording-config.ts`).
32458
32517
  */
32459
32518
  var RecordingStatusSchema = object({
32460
32519
  deviceId: number(),
package/dist/index.mjs CHANGED
@@ -15575,6 +15575,50 @@ var NodeProcessSchema = object({
15575
15575
  /** Wall-clock uptime (seconds). Parsed from `ps etime`. */
15576
15576
  uptimeSec: number()
15577
15577
  });
15578
+ /**
15579
+ * One retained container-memory reading.
15580
+ *
15581
+ * `atMs` is the timestamp of the PROCESS snapshot taken in the same tick, not
15582
+ * a second clock: that is what makes "processes sum to X, container says Y"
15583
+ * subtractable per point rather than an eyeballed comparison of two series
15584
+ * sampled at different instants.
15585
+ *
15586
+ * A reduced window keeps the sample with the LARGEST `currentBytes` in each
15587
+ * bucket, WHOLE. Taking a per-field maximum would synthesise a row whose parts
15588
+ * never coexisted, and a mean would smear away the peak this exists to find.
15589
+ */
15590
+ var ContainerMemoryPointSchema = object({
15591
+ /** Which hierarchy answered, so a reading is never ambiguous. */
15592
+ source: _enum(["cgroup-v2", "cgroup-v1"]),
15593
+ /** `memory.current` (v2) / `memory.usage_in_bytes` (v1). Always known. */
15594
+ currentBytes: number(),
15595
+ /** The cgroup's ceiling. `null` = NO LIMIT — never a sentinel, never zero. */
15596
+ limitBytes: number().nullable(),
15597
+ /** Anonymous pages: the closest thing to "what the processes allocated". */
15598
+ anonBytes: number().nullable(),
15599
+ /** Page cache. Charged to the cgroup, owned by no process. */
15600
+ fileBytes: number().nullable(),
15601
+ /**
15602
+ * Shared memory — and the field that explained the largest single surprise.
15603
+ * The i915 driver backs GPU buffers with shmem, so an inference pool or a
15604
+ * hardware-decode session holding DRM objects is charged HERE and appears
15605
+ * nowhere in a `ps` scan.
15606
+ */
15607
+ shmemBytes: number().nullable(),
15608
+ /** Kernel slab charged to this cgroup. `null` on v1, which never publishes it. */
15609
+ slabBytes: number().nullable(),
15610
+ /**
15611
+ * Shrinkable i915 GEM object bytes, from debugfs.
15612
+ *
15613
+ * **Host-wide across every DRM client, NOT cgroup-scoped.** It is not a
15614
+ * component of `currentBytes` and must not be subtracted from it; it says
15615
+ * what put the shmem there, where `shmemBytes` only says how much.
15616
+ *
15617
+ * `null` wherever debugfs is not mounted — which is inside every camstack
15618
+ * container today — and on any node with no Intel GPU.
15619
+ */
15620
+ gpuShmemBytes: number().nullable()
15621
+ }).extend({ atMs: number() });
15578
15622
  var DumpHeapSnapshotInputSchema = object({
15579
15623
  /** The addon whose runner should dump a heap snapshot. */
15580
15624
  addonId: string() });
@@ -15638,6 +15682,21 @@ var NodeLoadSeriesSchema = object({
15638
15682
  /** One entry per function seen in the window, heaviest-first. */
15639
15683
  series: array(LoadFunctionSeriesSchema).readonly(),
15640
15684
  /**
15685
+ * The CONTAINER's memory over the same window, oldest-first.
15686
+ *
15687
+ * Sits next to `series` rather than in a method of its own because the whole
15688
+ * question is a subtraction: the per-process rows in `series` sum to one
15689
+ * number and this one is another, and an operator who has to issue two calls
15690
+ * to compare them will compare two different instants. Same reader, same
15691
+ * `sinceMs`, same `bucketMs`, same timestamps.
15692
+ *
15693
+ * **EMPTY means ABSENT, never zero.** A node with no cgroup — a developer
15694
+ * Mac, a bare-metal host, a container with the hierarchy hidden — reports no
15695
+ * points at all. A zero here would be indistinguishable from a healthy
15696
+ * container and is precisely the lie this field exists to avoid.
15697
+ */
15698
+ containerMemory: array(ContainerMemoryPointSchema).readonly(),
15699
+ /**
15641
15700
  * Width of one returned bucket, in ms. Equals the sampling cadence when no
15642
15701
  * reduction was needed — so a caller can always say what one point covers
15643
15702
  * without having to know whether it was reduced.
@@ -32447,10 +32506,10 @@ var rebootCapability = {
32447
32506
  * recording config. NOTE on events (source of truth, R5/C3): this cap carries
32448
32507
  * NO event surface — `getPlaybackManifest` returns playlist URLs only. Timeline
32449
32508
  * events (motion/object/audio) come from `pipelineAnalytics` (durable SQLite
32450
- * rows); the recorder's internal EventMap markers are ephemeral in-RAM
32451
- * annotations that are not exposed here and must not be treated as an event
32452
- * feed. Event<->footage joins are by time, padded with the shared `EVENT_PAD_MS`
32453
- * (`interfaces/recording-config.ts`).
32509
+ * rows) and are the ONLY event surface the recorder has none. The in-RAM
32510
+ * playback markers it used to build were deleted on 2026-08-29 because nothing
32511
+ * ever read them. Event<->footage joins are by time, padded with the shared
32512
+ * `EVENT_PAD_MS` (`interfaces/recording-config.ts`).
32454
32513
  */
32455
32514
  var RecordingStatusSchema = object({
32456
32515
  deviceId: number(),
@@ -1,2 +1,2 @@
1
- import { n as e, t } from "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-CmYtdZEf.mjs";
1
+ import { n as e, t } from "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-BF_XPbUY.mjs";
2
2
  export { t as get, e as init };
@@ -2753,7 +2753,7 @@ async function rr(e) {
2753
2753
  }
2754
2754
  }
2755
2755
  async function ir() {
2756
- return tr ||= rr(() => import("./_virtual_mf-localSharedImportMap___mfe_internal__addon_osd_manager_page-esbRlHg_.mjs")).catch((e) => {
2756
+ return tr ||= rr(() => import("./_virtual_mf-localSharedImportMap___mfe_internal__addon_osd_manager_page-BiPHv48U.mjs")).catch((e) => {
2757
2757
  throw tr = void 0, e;
2758
2758
  }), tr;
2759
2759
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-osd-manager",
3
- "version": "0.1.32",
3
+ "version": "0.1.34",
4
4
  "description": "Binds camera on-screen-display slots to live state and recognitions",
5
5
  "keywords": [
6
6
  "camstack",