@camstack/addon-mqtt-broker 1.2.39 → 1.2.42
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/mqtt-broker.addon.js +69 -10
- package/dist/mqtt-broker.addon.mjs +69 -10
- package/package.json +1 -1
|
@@ -13696,6 +13696,50 @@ var NodeProcessSchema = object({
|
|
|
13696
13696
|
/** Wall-clock uptime (seconds). Parsed from `ps etime`. */
|
|
13697
13697
|
uptimeSec: number()
|
|
13698
13698
|
});
|
|
13699
|
+
/**
|
|
13700
|
+
* One retained container-memory reading.
|
|
13701
|
+
*
|
|
13702
|
+
* `atMs` is the timestamp of the PROCESS snapshot taken in the same tick, not
|
|
13703
|
+
* a second clock: that is what makes "processes sum to X, container says Y"
|
|
13704
|
+
* subtractable per point rather than an eyeballed comparison of two series
|
|
13705
|
+
* sampled at different instants.
|
|
13706
|
+
*
|
|
13707
|
+
* A reduced window keeps the sample with the LARGEST `currentBytes` in each
|
|
13708
|
+
* bucket, WHOLE. Taking a per-field maximum would synthesise a row whose parts
|
|
13709
|
+
* never coexisted, and a mean would smear away the peak this exists to find.
|
|
13710
|
+
*/
|
|
13711
|
+
var ContainerMemoryPointSchema = object({
|
|
13712
|
+
/** Which hierarchy answered, so a reading is never ambiguous. */
|
|
13713
|
+
source: _enum(["cgroup-v2", "cgroup-v1"]),
|
|
13714
|
+
/** `memory.current` (v2) / `memory.usage_in_bytes` (v1). Always known. */
|
|
13715
|
+
currentBytes: number(),
|
|
13716
|
+
/** The cgroup's ceiling. `null` = NO LIMIT — never a sentinel, never zero. */
|
|
13717
|
+
limitBytes: number().nullable(),
|
|
13718
|
+
/** Anonymous pages: the closest thing to "what the processes allocated". */
|
|
13719
|
+
anonBytes: number().nullable(),
|
|
13720
|
+
/** Page cache. Charged to the cgroup, owned by no process. */
|
|
13721
|
+
fileBytes: number().nullable(),
|
|
13722
|
+
/**
|
|
13723
|
+
* Shared memory — and the field that explained the largest single surprise.
|
|
13724
|
+
* The i915 driver backs GPU buffers with shmem, so an inference pool or a
|
|
13725
|
+
* hardware-decode session holding DRM objects is charged HERE and appears
|
|
13726
|
+
* nowhere in a `ps` scan.
|
|
13727
|
+
*/
|
|
13728
|
+
shmemBytes: number().nullable(),
|
|
13729
|
+
/** Kernel slab charged to this cgroup. `null` on v1, which never publishes it. */
|
|
13730
|
+
slabBytes: number().nullable(),
|
|
13731
|
+
/**
|
|
13732
|
+
* Shrinkable i915 GEM object bytes, from debugfs.
|
|
13733
|
+
*
|
|
13734
|
+
* **Host-wide across every DRM client, NOT cgroup-scoped.** It is not a
|
|
13735
|
+
* component of `currentBytes` and must not be subtracted from it; it says
|
|
13736
|
+
* what put the shmem there, where `shmemBytes` only says how much.
|
|
13737
|
+
*
|
|
13738
|
+
* `null` wherever debugfs is not mounted — which is inside every camstack
|
|
13739
|
+
* container today — and on any node with no Intel GPU.
|
|
13740
|
+
*/
|
|
13741
|
+
gpuShmemBytes: number().nullable()
|
|
13742
|
+
}).extend({ atMs: number() });
|
|
13699
13743
|
var DumpHeapSnapshotInputSchema = object({
|
|
13700
13744
|
/** The addon whose runner should dump a heap snapshot. */
|
|
13701
13745
|
addonId: string() });
|
|
@@ -13759,6 +13803,21 @@ var NodeLoadSeriesSchema = object({
|
|
|
13759
13803
|
/** One entry per function seen in the window, heaviest-first. */
|
|
13760
13804
|
series: array(LoadFunctionSeriesSchema).readonly(),
|
|
13761
13805
|
/**
|
|
13806
|
+
* The CONTAINER's memory over the same window, oldest-first.
|
|
13807
|
+
*
|
|
13808
|
+
* Sits next to `series` rather than in a method of its own because the whole
|
|
13809
|
+
* question is a subtraction: the per-process rows in `series` sum to one
|
|
13810
|
+
* number and this one is another, and an operator who has to issue two calls
|
|
13811
|
+
* to compare them will compare two different instants. Same reader, same
|
|
13812
|
+
* `sinceMs`, same `bucketMs`, same timestamps.
|
|
13813
|
+
*
|
|
13814
|
+
* **EMPTY means ABSENT, never zero.** A node with no cgroup — a developer
|
|
13815
|
+
* Mac, a bare-metal host, a container with the hierarchy hidden — reports no
|
|
13816
|
+
* points at all. A zero here would be indistinguishable from a healthy
|
|
13817
|
+
* container and is precisely the lie this field exists to avoid.
|
|
13818
|
+
*/
|
|
13819
|
+
containerMemory: array(ContainerMemoryPointSchema).readonly(),
|
|
13820
|
+
/**
|
|
13762
13821
|
* Width of one returned bucket, in ms. Equals the sampling cadence when no
|
|
13763
13822
|
* reduction was needed — so a caller can always say what one point covers
|
|
13764
13823
|
* without having to know whether it was reduced.
|
|
@@ -23656,23 +23715,23 @@ DeviceType.Camera, method(object({ deviceId: number() }), object({
|
|
|
23656
23715
|
sdpOffer: string()
|
|
23657
23716
|
}), {
|
|
23658
23717
|
kind: "mutation",
|
|
23659
|
-
auth: "
|
|
23718
|
+
auth: "protected"
|
|
23660
23719
|
}), method(object({
|
|
23661
23720
|
deviceId: number(),
|
|
23662
23721
|
sessionId: string(),
|
|
23663
23722
|
sdpAnswer: string()
|
|
23664
23723
|
}), _void(), {
|
|
23665
23724
|
kind: "mutation",
|
|
23666
|
-
auth: "
|
|
23725
|
+
auth: "protected"
|
|
23667
23726
|
}), method(object({
|
|
23668
23727
|
deviceId: number(),
|
|
23669
23728
|
sessionId: string()
|
|
23670
23729
|
}), _void(), {
|
|
23671
23730
|
kind: "mutation",
|
|
23672
|
-
auth: "
|
|
23731
|
+
auth: "protected"
|
|
23673
23732
|
}), method(object({ deviceId: number() }), object({ sessionId: string() }), {
|
|
23674
23733
|
kind: "mutation",
|
|
23675
|
-
auth: "
|
|
23734
|
+
auth: "protected"
|
|
23676
23735
|
}), method(object({
|
|
23677
23736
|
deviceId: number(),
|
|
23678
23737
|
/** Audio bytes for ONE frame, base64-encoded so the payload
|
|
@@ -23691,10 +23750,10 @@ DeviceType.Camera, method(object({ deviceId: number() }), object({
|
|
|
23691
23750
|
sequenceNumber: number().int()
|
|
23692
23751
|
}), object({ accepted: boolean() }), {
|
|
23693
23752
|
kind: "mutation",
|
|
23694
|
-
auth: "
|
|
23753
|
+
auth: "protected"
|
|
23695
23754
|
}), method(object({ deviceId: number() }), _void(), {
|
|
23696
23755
|
kind: "mutation",
|
|
23697
|
-
auth: "
|
|
23756
|
+
auth: "protected"
|
|
23698
23757
|
}), object({
|
|
23699
23758
|
deviceId: number(),
|
|
23700
23759
|
status: IntercomStatusSchema
|
|
@@ -25707,10 +25766,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
|
|
|
25707
25766
|
* recording config. NOTE on events (source of truth, R5/C3): this cap carries
|
|
25708
25767
|
* NO event surface — `getPlaybackManifest` returns playlist URLs only. Timeline
|
|
25709
25768
|
* events (motion/object/audio) come from `pipelineAnalytics` (durable SQLite
|
|
25710
|
-
* rows)
|
|
25711
|
-
*
|
|
25712
|
-
*
|
|
25713
|
-
* (`interfaces/recording-config.ts`).
|
|
25769
|
+
* rows) and are the ONLY event surface — the recorder has none. The in-RAM
|
|
25770
|
+
* playback markers it used to build were deleted on 2026-08-29 because nothing
|
|
25771
|
+
* ever read them. Event<->footage joins are by time, padded with the shared
|
|
25772
|
+
* `EVENT_PAD_MS` (`interfaces/recording-config.ts`).
|
|
25714
25773
|
*/
|
|
25715
25774
|
var RecordingStatusSchema = object({
|
|
25716
25775
|
deviceId: number(),
|
|
@@ -13691,6 +13691,50 @@ var NodeProcessSchema = object({
|
|
|
13691
13691
|
/** Wall-clock uptime (seconds). Parsed from `ps etime`. */
|
|
13692
13692
|
uptimeSec: number()
|
|
13693
13693
|
});
|
|
13694
|
+
/**
|
|
13695
|
+
* One retained container-memory reading.
|
|
13696
|
+
*
|
|
13697
|
+
* `atMs` is the timestamp of the PROCESS snapshot taken in the same tick, not
|
|
13698
|
+
* a second clock: that is what makes "processes sum to X, container says Y"
|
|
13699
|
+
* subtractable per point rather than an eyeballed comparison of two series
|
|
13700
|
+
* sampled at different instants.
|
|
13701
|
+
*
|
|
13702
|
+
* A reduced window keeps the sample with the LARGEST `currentBytes` in each
|
|
13703
|
+
* bucket, WHOLE. Taking a per-field maximum would synthesise a row whose parts
|
|
13704
|
+
* never coexisted, and a mean would smear away the peak this exists to find.
|
|
13705
|
+
*/
|
|
13706
|
+
var ContainerMemoryPointSchema = object({
|
|
13707
|
+
/** Which hierarchy answered, so a reading is never ambiguous. */
|
|
13708
|
+
source: _enum(["cgroup-v2", "cgroup-v1"]),
|
|
13709
|
+
/** `memory.current` (v2) / `memory.usage_in_bytes` (v1). Always known. */
|
|
13710
|
+
currentBytes: number(),
|
|
13711
|
+
/** The cgroup's ceiling. `null` = NO LIMIT — never a sentinel, never zero. */
|
|
13712
|
+
limitBytes: number().nullable(),
|
|
13713
|
+
/** Anonymous pages: the closest thing to "what the processes allocated". */
|
|
13714
|
+
anonBytes: number().nullable(),
|
|
13715
|
+
/** Page cache. Charged to the cgroup, owned by no process. */
|
|
13716
|
+
fileBytes: number().nullable(),
|
|
13717
|
+
/**
|
|
13718
|
+
* Shared memory — and the field that explained the largest single surprise.
|
|
13719
|
+
* The i915 driver backs GPU buffers with shmem, so an inference pool or a
|
|
13720
|
+
* hardware-decode session holding DRM objects is charged HERE and appears
|
|
13721
|
+
* nowhere in a `ps` scan.
|
|
13722
|
+
*/
|
|
13723
|
+
shmemBytes: number().nullable(),
|
|
13724
|
+
/** Kernel slab charged to this cgroup. `null` on v1, which never publishes it. */
|
|
13725
|
+
slabBytes: number().nullable(),
|
|
13726
|
+
/**
|
|
13727
|
+
* Shrinkable i915 GEM object bytes, from debugfs.
|
|
13728
|
+
*
|
|
13729
|
+
* **Host-wide across every DRM client, NOT cgroup-scoped.** It is not a
|
|
13730
|
+
* component of `currentBytes` and must not be subtracted from it; it says
|
|
13731
|
+
* what put the shmem there, where `shmemBytes` only says how much.
|
|
13732
|
+
*
|
|
13733
|
+
* `null` wherever debugfs is not mounted — which is inside every camstack
|
|
13734
|
+
* container today — and on any node with no Intel GPU.
|
|
13735
|
+
*/
|
|
13736
|
+
gpuShmemBytes: number().nullable()
|
|
13737
|
+
}).extend({ atMs: number() });
|
|
13694
13738
|
var DumpHeapSnapshotInputSchema = object({
|
|
13695
13739
|
/** The addon whose runner should dump a heap snapshot. */
|
|
13696
13740
|
addonId: string() });
|
|
@@ -13754,6 +13798,21 @@ var NodeLoadSeriesSchema = object({
|
|
|
13754
13798
|
/** One entry per function seen in the window, heaviest-first. */
|
|
13755
13799
|
series: array(LoadFunctionSeriesSchema).readonly(),
|
|
13756
13800
|
/**
|
|
13801
|
+
* The CONTAINER's memory over the same window, oldest-first.
|
|
13802
|
+
*
|
|
13803
|
+
* Sits next to `series` rather than in a method of its own because the whole
|
|
13804
|
+
* question is a subtraction: the per-process rows in `series` sum to one
|
|
13805
|
+
* number and this one is another, and an operator who has to issue two calls
|
|
13806
|
+
* to compare them will compare two different instants. Same reader, same
|
|
13807
|
+
* `sinceMs`, same `bucketMs`, same timestamps.
|
|
13808
|
+
*
|
|
13809
|
+
* **EMPTY means ABSENT, never zero.** A node with no cgroup — a developer
|
|
13810
|
+
* Mac, a bare-metal host, a container with the hierarchy hidden — reports no
|
|
13811
|
+
* points at all. A zero here would be indistinguishable from a healthy
|
|
13812
|
+
* container and is precisely the lie this field exists to avoid.
|
|
13813
|
+
*/
|
|
13814
|
+
containerMemory: array(ContainerMemoryPointSchema).readonly(),
|
|
13815
|
+
/**
|
|
13757
13816
|
* Width of one returned bucket, in ms. Equals the sampling cadence when no
|
|
13758
13817
|
* reduction was needed — so a caller can always say what one point covers
|
|
13759
13818
|
* without having to know whether it was reduced.
|
|
@@ -23651,23 +23710,23 @@ DeviceType.Camera, method(object({ deviceId: number() }), object({
|
|
|
23651
23710
|
sdpOffer: string()
|
|
23652
23711
|
}), {
|
|
23653
23712
|
kind: "mutation",
|
|
23654
|
-
auth: "
|
|
23713
|
+
auth: "protected"
|
|
23655
23714
|
}), method(object({
|
|
23656
23715
|
deviceId: number(),
|
|
23657
23716
|
sessionId: string(),
|
|
23658
23717
|
sdpAnswer: string()
|
|
23659
23718
|
}), _void(), {
|
|
23660
23719
|
kind: "mutation",
|
|
23661
|
-
auth: "
|
|
23720
|
+
auth: "protected"
|
|
23662
23721
|
}), method(object({
|
|
23663
23722
|
deviceId: number(),
|
|
23664
23723
|
sessionId: string()
|
|
23665
23724
|
}), _void(), {
|
|
23666
23725
|
kind: "mutation",
|
|
23667
|
-
auth: "
|
|
23726
|
+
auth: "protected"
|
|
23668
23727
|
}), method(object({ deviceId: number() }), object({ sessionId: string() }), {
|
|
23669
23728
|
kind: "mutation",
|
|
23670
|
-
auth: "
|
|
23729
|
+
auth: "protected"
|
|
23671
23730
|
}), method(object({
|
|
23672
23731
|
deviceId: number(),
|
|
23673
23732
|
/** Audio bytes for ONE frame, base64-encoded so the payload
|
|
@@ -23686,10 +23745,10 @@ DeviceType.Camera, method(object({ deviceId: number() }), object({
|
|
|
23686
23745
|
sequenceNumber: number().int()
|
|
23687
23746
|
}), object({ accepted: boolean() }), {
|
|
23688
23747
|
kind: "mutation",
|
|
23689
|
-
auth: "
|
|
23748
|
+
auth: "protected"
|
|
23690
23749
|
}), method(object({ deviceId: number() }), _void(), {
|
|
23691
23750
|
kind: "mutation",
|
|
23692
|
-
auth: "
|
|
23751
|
+
auth: "protected"
|
|
23693
23752
|
}), object({
|
|
23694
23753
|
deviceId: number(),
|
|
23695
23754
|
status: IntercomStatusSchema
|
|
@@ -25702,10 +25761,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
|
|
|
25702
25761
|
* recording config. NOTE on events (source of truth, R5/C3): this cap carries
|
|
25703
25762
|
* NO event surface — `getPlaybackManifest` returns playlist URLs only. Timeline
|
|
25704
25763
|
* events (motion/object/audio) come from `pipelineAnalytics` (durable SQLite
|
|
25705
|
-
* rows)
|
|
25706
|
-
*
|
|
25707
|
-
*
|
|
25708
|
-
* (`interfaces/recording-config.ts`).
|
|
25764
|
+
* rows) and are the ONLY event surface — the recorder has none. The in-RAM
|
|
25765
|
+
* playback markers it used to build were deleted on 2026-08-29 because nothing
|
|
25766
|
+
* ever read them. Event<->footage joins are by time, padded with the shared
|
|
25767
|
+
* `EVENT_PAD_MS` (`interfaces/recording-config.ts`).
|
|
25709
25768
|
*/
|
|
25710
25769
|
var RecordingStatusSchema = object({
|
|
25711
25770
|
deviceId: number(),
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@camstack/addon-mqtt-broker",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.42",
|
|
4
4
|
"description": "MQTT broker registry addon for CamStack — manages external broker entries + an optional embedded aedes broker. Consumers spin up their own `mqtt.js` clients via the `mqtt-broker` cap.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"camstack",
|