agent-sanitizer 2.43.8 → 2.43.10
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.
|
@@ -217,6 +217,10 @@ export function startHookTimer(now = Date.now, cpuNow = processCpuMs) {
|
|
|
217
217
|
* than asserting an attribution nothing measured: a wall-clock overrun on a
|
|
218
218
|
* loaded host is the common case, and blaming it on the sanitizer sends the
|
|
219
219
|
* operator hunting a per-call cost that does not exist.
|
|
220
|
+
*
|
|
221
|
+
* The wait clause names candidates and picks none, for the same reason. A hook
|
|
222
|
+
* that blocks on a dead socket inside a HOST extension spends no CPU and no
|
|
223
|
+
* machine load, so naming either as the cause would be a second wrong guess.
|
|
220
224
|
* @param {string} hookName
|
|
221
225
|
* @param {number} elapsedMs
|
|
222
226
|
* @param {number} [thresholdMs]
|
|
@@ -236,7 +240,7 @@ export function slowHookNotice(
|
|
|
236
240
|
const attribution =
|
|
237
241
|
typeof cpuMs === "number"
|
|
238
242
|
? `, and used ${formatSeconds(cpuMs)}s of CPU. ` +
|
|
239
|
-
"Only the CPU share is work every affected call repeats; the rest was waiting on a busy machine."
|
|
243
|
+
"Only the CPU share is work every affected call repeats; the rest was spent waiting, on a busy machine or on something this hook called."
|
|
240
244
|
: ". Wall-clock alone cannot separate the sanitizer's own work from a busy machine.";
|
|
241
245
|
return (
|
|
242
246
|
`agent-sanitizer PERFORMANCE: the ${hookName} hook took ` +
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "agent-sanitizer",
|
|
3
|
-
"version": "2.43.
|
|
3
|
+
"version": "2.43.10",
|
|
4
4
|
"description": "Defend an agent against hidden-content injection: strip payload-capable invisible Unicode and ANSI, splice out human-invisible HTML, and flag data-exfil URLs in untrusted text before any model sees it.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"repository": {
|
|
@@ -74,6 +74,10 @@ export function startHookTimer(now?: () => number, cpuNow?: () => number): {
|
|
|
74
74
|
* than asserting an attribution nothing measured: a wall-clock overrun on a
|
|
75
75
|
* loaded host is the common case, and blaming it on the sanitizer sends the
|
|
76
76
|
* operator hunting a per-call cost that does not exist.
|
|
77
|
+
*
|
|
78
|
+
* The wait clause names candidates and picks none, for the same reason. A hook
|
|
79
|
+
* that blocks on a dead socket inside a HOST extension spends no CPU and no
|
|
80
|
+
* machine load, so naming either as the cause would be a second wrong guess.
|
|
77
81
|
* @param {string} hookName
|
|
78
82
|
* @param {number} elapsedMs
|
|
79
83
|
* @param {number} [thresholdMs]
|