teapot-coding-agent 0.37.17 → 0.37.18
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/master.js +9 -1
- package/package.json +1 -1
- package/public/assets/{index-LTvn2Be9.js → index-CCy4gAi8.js} +4 -4
- package/public/assets/{index-LTvn2Be9.js.map → index-CCy4gAi8.js.map} +1 -1
- package/public/assets/{shiki--crGONDM.js → shiki-wIAUQXJx.js} +2 -2
- package/public/assets/{shiki--crGONDM.js.map → shiki-wIAUQXJx.js.map} +1 -1
- package/public/index.html +1 -1
package/dist/master.js
CHANGED
|
@@ -2315,7 +2315,15 @@ When this task is done (or truly blocked), call finish() with a summary for @${p
|
|
|
2315
2315
|
uptimeSec: Math.floor((Date.now() - this.startedAt) / 1000),
|
|
2316
2316
|
rssMb: +(mu.rss / 1048576).toFixed(1),
|
|
2317
2317
|
heapUsedMb: +(mu.heapUsed / 1048576).toFixed(1),
|
|
2318
|
-
|
|
2318
|
+
/**
|
|
2319
|
+
* `process.cpuUsage()` reports MICROseconds, so this is divided by 1000.
|
|
2320
|
+
*
|
|
2321
|
+
* The field is named `cpuMsTotal` and was not converted, so it read 1000x too high — a
|
|
2322
|
+
* 1900-second-old process reported 18,313,198 "ms" against a real 18,310ms of CPU, which
|
|
2323
|
+
* looks like 9.6 cores burning continuously. That is how a healthy idle server got
|
|
2324
|
+
* investigated as a runaway loop.
|
|
2325
|
+
*/
|
|
2326
|
+
cpuMsTotal: Math.round((cu.user + cu.system) / 1000),
|
|
2319
2327
|
loadavg1: +(os.loadavg()[0]).toFixed(2),
|
|
2320
2328
|
agents: [...this.agents.values()].map((a) => ({
|
|
2321
2329
|
id: a.opts_id(),
|