@camstack/addon-export-alexa 1.2.45 → 1.2.48
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/export-alexa.addon.js +69 -10
- package/dist/export-alexa.addon.mjs +69 -10
- package/package.json +1 -1
|
@@ -13913,6 +13913,50 @@ var NodeProcessSchema = object({
|
|
|
13913
13913
|
/** Wall-clock uptime (seconds). Parsed from `ps etime`. */
|
|
13914
13914
|
uptimeSec: number()
|
|
13915
13915
|
});
|
|
13916
|
+
/**
|
|
13917
|
+
* One retained container-memory reading.
|
|
13918
|
+
*
|
|
13919
|
+
* `atMs` is the timestamp of the PROCESS snapshot taken in the same tick, not
|
|
13920
|
+
* a second clock: that is what makes "processes sum to X, container says Y"
|
|
13921
|
+
* subtractable per point rather than an eyeballed comparison of two series
|
|
13922
|
+
* sampled at different instants.
|
|
13923
|
+
*
|
|
13924
|
+
* A reduced window keeps the sample with the LARGEST `currentBytes` in each
|
|
13925
|
+
* bucket, WHOLE. Taking a per-field maximum would synthesise a row whose parts
|
|
13926
|
+
* never coexisted, and a mean would smear away the peak this exists to find.
|
|
13927
|
+
*/
|
|
13928
|
+
var ContainerMemoryPointSchema = object({
|
|
13929
|
+
/** Which hierarchy answered, so a reading is never ambiguous. */
|
|
13930
|
+
source: _enum(["cgroup-v2", "cgroup-v1"]),
|
|
13931
|
+
/** `memory.current` (v2) / `memory.usage_in_bytes` (v1). Always known. */
|
|
13932
|
+
currentBytes: number(),
|
|
13933
|
+
/** The cgroup's ceiling. `null` = NO LIMIT — never a sentinel, never zero. */
|
|
13934
|
+
limitBytes: number().nullable(),
|
|
13935
|
+
/** Anonymous pages: the closest thing to "what the processes allocated". */
|
|
13936
|
+
anonBytes: number().nullable(),
|
|
13937
|
+
/** Page cache. Charged to the cgroup, owned by no process. */
|
|
13938
|
+
fileBytes: number().nullable(),
|
|
13939
|
+
/**
|
|
13940
|
+
* Shared memory — and the field that explained the largest single surprise.
|
|
13941
|
+
* The i915 driver backs GPU buffers with shmem, so an inference pool or a
|
|
13942
|
+
* hardware-decode session holding DRM objects is charged HERE and appears
|
|
13943
|
+
* nowhere in a `ps` scan.
|
|
13944
|
+
*/
|
|
13945
|
+
shmemBytes: number().nullable(),
|
|
13946
|
+
/** Kernel slab charged to this cgroup. `null` on v1, which never publishes it. */
|
|
13947
|
+
slabBytes: number().nullable(),
|
|
13948
|
+
/**
|
|
13949
|
+
* Shrinkable i915 GEM object bytes, from debugfs.
|
|
13950
|
+
*
|
|
13951
|
+
* **Host-wide across every DRM client, NOT cgroup-scoped.** It is not a
|
|
13952
|
+
* component of `currentBytes` and must not be subtracted from it; it says
|
|
13953
|
+
* what put the shmem there, where `shmemBytes` only says how much.
|
|
13954
|
+
*
|
|
13955
|
+
* `null` wherever debugfs is not mounted — which is inside every camstack
|
|
13956
|
+
* container today — and on any node with no Intel GPU.
|
|
13957
|
+
*/
|
|
13958
|
+
gpuShmemBytes: number().nullable()
|
|
13959
|
+
}).extend({ atMs: number() });
|
|
13916
13960
|
var DumpHeapSnapshotInputSchema = object({
|
|
13917
13961
|
/** The addon whose runner should dump a heap snapshot. */
|
|
13918
13962
|
addonId: string() });
|
|
@@ -13976,6 +14020,21 @@ var NodeLoadSeriesSchema = object({
|
|
|
13976
14020
|
/** One entry per function seen in the window, heaviest-first. */
|
|
13977
14021
|
series: array(LoadFunctionSeriesSchema).readonly(),
|
|
13978
14022
|
/**
|
|
14023
|
+
* The CONTAINER's memory over the same window, oldest-first.
|
|
14024
|
+
*
|
|
14025
|
+
* Sits next to `series` rather than in a method of its own because the whole
|
|
14026
|
+
* question is a subtraction: the per-process rows in `series` sum to one
|
|
14027
|
+
* number and this one is another, and an operator who has to issue two calls
|
|
14028
|
+
* to compare them will compare two different instants. Same reader, same
|
|
14029
|
+
* `sinceMs`, same `bucketMs`, same timestamps.
|
|
14030
|
+
*
|
|
14031
|
+
* **EMPTY means ABSENT, never zero.** A node with no cgroup — a developer
|
|
14032
|
+
* Mac, a bare-metal host, a container with the hierarchy hidden — reports no
|
|
14033
|
+
* points at all. A zero here would be indistinguishable from a healthy
|
|
14034
|
+
* container and is precisely the lie this field exists to avoid.
|
|
14035
|
+
*/
|
|
14036
|
+
containerMemory: array(ContainerMemoryPointSchema).readonly(),
|
|
14037
|
+
/**
|
|
13979
14038
|
* Width of one returned bucket, in ms. Equals the sampling cadence when no
|
|
13980
14039
|
* reduction was needed — so a caller can always say what one point covers
|
|
13981
14040
|
* without having to know whether it was reduced.
|
|
@@ -23870,23 +23929,23 @@ DeviceType.Camera, method(object({ deviceId: number() }), object({
|
|
|
23870
23929
|
sdpOffer: string()
|
|
23871
23930
|
}), {
|
|
23872
23931
|
kind: "mutation",
|
|
23873
|
-
auth: "
|
|
23932
|
+
auth: "protected"
|
|
23874
23933
|
}), method(object({
|
|
23875
23934
|
deviceId: number(),
|
|
23876
23935
|
sessionId: string(),
|
|
23877
23936
|
sdpAnswer: string()
|
|
23878
23937
|
}), _void(), {
|
|
23879
23938
|
kind: "mutation",
|
|
23880
|
-
auth: "
|
|
23939
|
+
auth: "protected"
|
|
23881
23940
|
}), method(object({
|
|
23882
23941
|
deviceId: number(),
|
|
23883
23942
|
sessionId: string()
|
|
23884
23943
|
}), _void(), {
|
|
23885
23944
|
kind: "mutation",
|
|
23886
|
-
auth: "
|
|
23945
|
+
auth: "protected"
|
|
23887
23946
|
}), method(object({ deviceId: number() }), object({ sessionId: string() }), {
|
|
23888
23947
|
kind: "mutation",
|
|
23889
|
-
auth: "
|
|
23948
|
+
auth: "protected"
|
|
23890
23949
|
}), method(object({
|
|
23891
23950
|
deviceId: number(),
|
|
23892
23951
|
/** Audio bytes for ONE frame, base64-encoded so the payload
|
|
@@ -23905,10 +23964,10 @@ DeviceType.Camera, method(object({ deviceId: number() }), object({
|
|
|
23905
23964
|
sequenceNumber: number().int()
|
|
23906
23965
|
}), object({ accepted: boolean() }), {
|
|
23907
23966
|
kind: "mutation",
|
|
23908
|
-
auth: "
|
|
23967
|
+
auth: "protected"
|
|
23909
23968
|
}), method(object({ deviceId: number() }), _void(), {
|
|
23910
23969
|
kind: "mutation",
|
|
23911
|
-
auth: "
|
|
23970
|
+
auth: "protected"
|
|
23912
23971
|
}), object({
|
|
23913
23972
|
deviceId: number(),
|
|
23914
23973
|
status: IntercomStatusSchema
|
|
@@ -25921,10 +25980,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
|
|
|
25921
25980
|
* recording config. NOTE on events (source of truth, R5/C3): this cap carries
|
|
25922
25981
|
* NO event surface — `getPlaybackManifest` returns playlist URLs only. Timeline
|
|
25923
25982
|
* events (motion/object/audio) come from `pipelineAnalytics` (durable SQLite
|
|
25924
|
-
* rows)
|
|
25925
|
-
*
|
|
25926
|
-
*
|
|
25927
|
-
* (`interfaces/recording-config.ts`).
|
|
25983
|
+
* rows) and are the ONLY event surface — the recorder has none. The in-RAM
|
|
25984
|
+
* playback markers it used to build were deleted on 2026-08-29 because nothing
|
|
25985
|
+
* ever read them. Event<->footage joins are by time, padded with the shared
|
|
25986
|
+
* `EVENT_PAD_MS` (`interfaces/recording-config.ts`).
|
|
25928
25987
|
*/
|
|
25929
25988
|
var RecordingStatusSchema = object({
|
|
25930
25989
|
deviceId: number(),
|
|
@@ -13886,6 +13886,50 @@ var NodeProcessSchema = object({
|
|
|
13886
13886
|
/** Wall-clock uptime (seconds). Parsed from `ps etime`. */
|
|
13887
13887
|
uptimeSec: number()
|
|
13888
13888
|
});
|
|
13889
|
+
/**
|
|
13890
|
+
* One retained container-memory reading.
|
|
13891
|
+
*
|
|
13892
|
+
* `atMs` is the timestamp of the PROCESS snapshot taken in the same tick, not
|
|
13893
|
+
* a second clock: that is what makes "processes sum to X, container says Y"
|
|
13894
|
+
* subtractable per point rather than an eyeballed comparison of two series
|
|
13895
|
+
* sampled at different instants.
|
|
13896
|
+
*
|
|
13897
|
+
* A reduced window keeps the sample with the LARGEST `currentBytes` in each
|
|
13898
|
+
* bucket, WHOLE. Taking a per-field maximum would synthesise a row whose parts
|
|
13899
|
+
* never coexisted, and a mean would smear away the peak this exists to find.
|
|
13900
|
+
*/
|
|
13901
|
+
var ContainerMemoryPointSchema = object({
|
|
13902
|
+
/** Which hierarchy answered, so a reading is never ambiguous. */
|
|
13903
|
+
source: _enum(["cgroup-v2", "cgroup-v1"]),
|
|
13904
|
+
/** `memory.current` (v2) / `memory.usage_in_bytes` (v1). Always known. */
|
|
13905
|
+
currentBytes: number(),
|
|
13906
|
+
/** The cgroup's ceiling. `null` = NO LIMIT — never a sentinel, never zero. */
|
|
13907
|
+
limitBytes: number().nullable(),
|
|
13908
|
+
/** Anonymous pages: the closest thing to "what the processes allocated". */
|
|
13909
|
+
anonBytes: number().nullable(),
|
|
13910
|
+
/** Page cache. Charged to the cgroup, owned by no process. */
|
|
13911
|
+
fileBytes: number().nullable(),
|
|
13912
|
+
/**
|
|
13913
|
+
* Shared memory — and the field that explained the largest single surprise.
|
|
13914
|
+
* The i915 driver backs GPU buffers with shmem, so an inference pool or a
|
|
13915
|
+
* hardware-decode session holding DRM objects is charged HERE and appears
|
|
13916
|
+
* nowhere in a `ps` scan.
|
|
13917
|
+
*/
|
|
13918
|
+
shmemBytes: number().nullable(),
|
|
13919
|
+
/** Kernel slab charged to this cgroup. `null` on v1, which never publishes it. */
|
|
13920
|
+
slabBytes: number().nullable(),
|
|
13921
|
+
/**
|
|
13922
|
+
* Shrinkable i915 GEM object bytes, from debugfs.
|
|
13923
|
+
*
|
|
13924
|
+
* **Host-wide across every DRM client, NOT cgroup-scoped.** It is not a
|
|
13925
|
+
* component of `currentBytes` and must not be subtracted from it; it says
|
|
13926
|
+
* what put the shmem there, where `shmemBytes` only says how much.
|
|
13927
|
+
*
|
|
13928
|
+
* `null` wherever debugfs is not mounted — which is inside every camstack
|
|
13929
|
+
* container today — and on any node with no Intel GPU.
|
|
13930
|
+
*/
|
|
13931
|
+
gpuShmemBytes: number().nullable()
|
|
13932
|
+
}).extend({ atMs: number() });
|
|
13889
13933
|
var DumpHeapSnapshotInputSchema = object({
|
|
13890
13934
|
/** The addon whose runner should dump a heap snapshot. */
|
|
13891
13935
|
addonId: string() });
|
|
@@ -13949,6 +13993,21 @@ var NodeLoadSeriesSchema = object({
|
|
|
13949
13993
|
/** One entry per function seen in the window, heaviest-first. */
|
|
13950
13994
|
series: array(LoadFunctionSeriesSchema).readonly(),
|
|
13951
13995
|
/**
|
|
13996
|
+
* The CONTAINER's memory over the same window, oldest-first.
|
|
13997
|
+
*
|
|
13998
|
+
* Sits next to `series` rather than in a method of its own because the whole
|
|
13999
|
+
* question is a subtraction: the per-process rows in `series` sum to one
|
|
14000
|
+
* number and this one is another, and an operator who has to issue two calls
|
|
14001
|
+
* to compare them will compare two different instants. Same reader, same
|
|
14002
|
+
* `sinceMs`, same `bucketMs`, same timestamps.
|
|
14003
|
+
*
|
|
14004
|
+
* **EMPTY means ABSENT, never zero.** A node with no cgroup — a developer
|
|
14005
|
+
* Mac, a bare-metal host, a container with the hierarchy hidden — reports no
|
|
14006
|
+
* points at all. A zero here would be indistinguishable from a healthy
|
|
14007
|
+
* container and is precisely the lie this field exists to avoid.
|
|
14008
|
+
*/
|
|
14009
|
+
containerMemory: array(ContainerMemoryPointSchema).readonly(),
|
|
14010
|
+
/**
|
|
13952
14011
|
* Width of one returned bucket, in ms. Equals the sampling cadence when no
|
|
13953
14012
|
* reduction was needed — so a caller can always say what one point covers
|
|
13954
14013
|
* without having to know whether it was reduced.
|
|
@@ -23843,23 +23902,23 @@ DeviceType.Camera, method(object({ deviceId: number() }), object({
|
|
|
23843
23902
|
sdpOffer: string()
|
|
23844
23903
|
}), {
|
|
23845
23904
|
kind: "mutation",
|
|
23846
|
-
auth: "
|
|
23905
|
+
auth: "protected"
|
|
23847
23906
|
}), method(object({
|
|
23848
23907
|
deviceId: number(),
|
|
23849
23908
|
sessionId: string(),
|
|
23850
23909
|
sdpAnswer: string()
|
|
23851
23910
|
}), _void(), {
|
|
23852
23911
|
kind: "mutation",
|
|
23853
|
-
auth: "
|
|
23912
|
+
auth: "protected"
|
|
23854
23913
|
}), method(object({
|
|
23855
23914
|
deviceId: number(),
|
|
23856
23915
|
sessionId: string()
|
|
23857
23916
|
}), _void(), {
|
|
23858
23917
|
kind: "mutation",
|
|
23859
|
-
auth: "
|
|
23918
|
+
auth: "protected"
|
|
23860
23919
|
}), method(object({ deviceId: number() }), object({ sessionId: string() }), {
|
|
23861
23920
|
kind: "mutation",
|
|
23862
|
-
auth: "
|
|
23921
|
+
auth: "protected"
|
|
23863
23922
|
}), method(object({
|
|
23864
23923
|
deviceId: number(),
|
|
23865
23924
|
/** Audio bytes for ONE frame, base64-encoded so the payload
|
|
@@ -23878,10 +23937,10 @@ DeviceType.Camera, method(object({ deviceId: number() }), object({
|
|
|
23878
23937
|
sequenceNumber: number().int()
|
|
23879
23938
|
}), object({ accepted: boolean() }), {
|
|
23880
23939
|
kind: "mutation",
|
|
23881
|
-
auth: "
|
|
23940
|
+
auth: "protected"
|
|
23882
23941
|
}), method(object({ deviceId: number() }), _void(), {
|
|
23883
23942
|
kind: "mutation",
|
|
23884
|
-
auth: "
|
|
23943
|
+
auth: "protected"
|
|
23885
23944
|
}), object({
|
|
23886
23945
|
deviceId: number(),
|
|
23887
23946
|
status: IntercomStatusSchema
|
|
@@ -25894,10 +25953,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
|
|
|
25894
25953
|
* recording config. NOTE on events (source of truth, R5/C3): this cap carries
|
|
25895
25954
|
* NO event surface — `getPlaybackManifest` returns playlist URLs only. Timeline
|
|
25896
25955
|
* events (motion/object/audio) come from `pipelineAnalytics` (durable SQLite
|
|
25897
|
-
* rows)
|
|
25898
|
-
*
|
|
25899
|
-
*
|
|
25900
|
-
* (`interfaces/recording-config.ts`).
|
|
25956
|
+
* rows) and are the ONLY event surface — the recorder has none. The in-RAM
|
|
25957
|
+
* playback markers it used to build were deleted on 2026-08-29 because nothing
|
|
25958
|
+
* ever read them. Event<->footage joins are by time, padded with the shared
|
|
25959
|
+
* `EVENT_PAD_MS` (`interfaces/recording-config.ts`).
|
|
25901
25960
|
*/
|
|
25902
25961
|
var RecordingStatusSchema = object({
|
|
25903
25962
|
deviceId: number(),
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@camstack/addon-export-alexa",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.48",
|
|
4
4
|
"description": "Alexa Smart Home Skill export — hub-side OAuth provider + directive handler. The companion AWS Lambda forwards Alexa directives to this addon's /addon/export-alexa/directive endpoint.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"camstack",
|