kimi-plugin-cc 2.0.7

package/plugins/kimi-codex/dist/background-spawn.js

@@ -0,0 +1,224 @@
+import { spawn } from "node:child_process";
+import { access, appendFile, constants as fsConstants } from "node:fs/promises";
+import path from "node:path";
+import { fileURLToPath } from "node:url";
+import { RuntimeError, formatError } from "./errors.js";
+import { preferStableNodePath } from "./hooks/install-paths.js";
+import { markJobFailed, waitForTerminalJob } from "./jobs.js";
+import { JobStore } from "./job-store.js";
+import { readArtifact } from "./render.js";
+// Resolves to runtime/companion.ts in dev (via tsx) and dist/companion.js in production (compiled
+// with tsc to the same relative layout). The extension is derived from the running module so the
+// child-process spawn in startBackgroundJob targets the right entrypoint in both modes.
+const isCompiledRuntime = import.meta.url.endsWith(".js");
+const companionEntrypoint = fileURLToPath(new URL(isCompiledRuntime ? "./companion.js" : "./companion.ts", import.meta.url));
+const companionProjectRoot = path.resolve(path.dirname(companionEntrypoint), "..");
+const FAILURE_PERSIST_RETRY_DELAYS_MS = [100, 200, 400];
+export async function startBackgroundJob(job, prompt, context, paths, options) {
+    // MUST be the same resolution the hook verifier uses. The worker re-verifies
+    // the hook (rescue.ts / ask.ts, deliberately, so a background job cannot
+    // outlive or bypass the check), and the verifier rebuilds the canonical
+    // command from ITS OWN `process.argv0`. Spawning with a different spelling of
+    // node than setup pinned makes the worker compute a different expected
+    // command than the config holds → byte-exact mismatch → every background
+    // rescue/ask refuses forever, with `/kimi:setup` unable to converge the two
+    // sides (setup runs via companion.sh, whose argv0 is the stable symlink).
+    //
+    // Concretely: `spawn(process.execPath)` gives the child an argv0 equal to the
+    // fully symlink-resolved path (…/Cellar/node/<ver>/bin/node), whereas setup
+    // pins /opt/homebrew/bin/node. Caught by Kimi's pre-release review of v1.9.0.
+    // NOTE: this is deliberately NOT `resolveNodeBinary`, which additionally
+    // REQUIRES an absolute override because the hook command runs under
+    // `/bin/sh -c` with a possibly sanitized PATH. Spawning has no such
+    // constraint — a bare name is resolved by spawn() via PATH — so the override
+    // is honored verbatim here. Only the no-override default needs to change:
+    // it must match what the verifier computes, hence `preferStableNodePath`.
+    const override = context.env.KIMI_PLUGIN_CC_NODE_BIN;
+    const nodeBinary = override !== undefined && override.length > 0
+        ? override
+        : preferStableNodePath(process.execPath);
+    // Only fast-path the `fs.access` check for absolute/relative paths. A bare
+    // name like "node" is resolved by spawn() via PATH; the spawn `error` listener
+    // will still surface ENOENT on nextTick for that path, classified as
+    // spawnFailedErrorCode via the listener below.
+    if (nodeBinary.includes("/") || nodeBinary.includes("\\")) {
+        try {
+            await access(nodeBinary, fsConstants.X_OK);
+        }
+        catch (accessError) {
+            const code = accessError.code;
+            if (code === "ENOENT" || code === "EACCES" || code === "EPERM") {
+                const classified = new RuntimeError(options.nodeBinInvalidErrorCode, `Configured Node binary is not executable: ${nodeBinary}. Set KIMI_PLUGIN_CC_NODE_BIN to a valid Node >=22.5 executable and retry.`, options.spawnStage, accessError instanceof Error ? { cause: accessError } : undefined);
+                await persistBackgroundFailure(paths, job.job_id, classified, options.failedSummary, "node-bin-invalid");
+                throw classified;
+            }
+            // Any other errno (EIO, etc.) — fall through to the spawn attempt and let the
+            // existing spawn error path surface it.
+        }
+    }
+    const b64 = Buffer.from(prompt, "utf8").toString("base64");
+    const spawnArgs = isCompiledRuntime
+        ? [companionEntrypoint, "worker", options.workerKind, job.job_id]
+        : ["--import", "tsx", companionEntrypoint, "worker", options.workerKind, job.job_id];
+    const child = spawn(nodeBinary, spawnArgs, {
+        cwd: companionProjectRoot,
+        detached: true,
+        stdio: "ignore",
+        env: {
+            ...context.env,
+            KIMI_PLUGIN_CC_WORKSPACE_CWD: context.cwd,
+            [options.promptEnvVar]: b64,
+            [options.reusedSessionEnvVar]: options.reusedSession ? "1" : "0",
+            ...(options.extraEnv ?? {}),
+            // A worker must reopen the exact store its parent selected, regardless of cwd.
+            KIMI_PLUGIN_CC_DATA: path.resolve(paths.claudePluginData),
+        },
+    });
+    let spawnReportedFailure = false;
+    const spawnErrorPromise = new Promise((resolve) => {
+        let settled = false;
+        const settle = (value) => {
+            if (settled) {
+                return;
+            }
+            settled = true;
+            resolve(value);
+        };
+        child.once("error", (spawnError) => {
+            spawnReportedFailure = true;
+            settle(new RuntimeError(options.spawnFailedErrorCode, `Background ${options.workerKind} worker failed to spawn: ${spawnError.message}`, options.spawnStage, { cause: spawnError }));
+        });
+        // Give the event loop one tick to deliver a synchronous spawn error
+        // (ENOENT fires on process.nextTick). If nothing fires by then, the
+        // child is live and we can proceed.
+        setImmediate(() => settle(null));
+    });
+    child.on("close", (exitCode, signal) => {
+        if (spawnReportedFailure) {
+            return;
+        }
+        if (exitCode === null || exitCode === 0) {
+            return;
+        }
+        // The worker exited non-zero before any state update. If the job is
+        // still in its spawn phase, the worker never reached executeJob.
+        const classified = new RuntimeError(options.earlyExitErrorCode, `Background ${options.workerKind} worker exited with code ${exitCode}${signal ? ` (signal ${signal})` : ""} before reporting a result.`, options.spawnStage);
+        void markEarlyExit(paths, job.job_id, classified, options.failedSummary);
+    });
+    child.unref();
+    const spawnError = await spawnErrorPromise;
+    if (spawnError) {
+        await markSpawnFailure(paths, job.job_id, spawnError, options.failedSummary);
+        throw spawnError;
+    }
+    const store = new JobStore(paths);
+    try {
+        store.updateRunningJob(job.job_id, {
+            pid: child.pid ?? null,
+            phase: "worker-spawned",
+        });
+    }
+    finally {
+        store.close();
+    }
+    if (options.wait) {
+        const completed = await waitForTerminalJob(() => new JobStore(paths), job.job_id);
+        if (!completed.final_output_path) {
+            throw new RuntimeError(options.missingResultErrorCode, describeMissingResult(completed, options.workerKind), options.waitStage);
+        }
+        return readArtifact(completed.final_output_path);
+    }
+    return `${JSON.stringify({
+        job_id: job.job_id,
+        command_type: job.command_type,
+    }, null, 2)}\n`;
+}
+async function markSpawnFailure(paths, jobId, classified, failedSummary) {
+    await persistBackgroundFailure(paths, jobId, classified, failedSummary, "spawn-failed");
+}
+async function markEarlyExit(paths, jobId, classified, failedSummary) {
+    await persistBackgroundFailure(paths, jobId, classified, failedSummary, "early-exit", (current) => {
+        // Only mark failure if the worker exited before advancing past the spawn phase.
+        // Once the worker reaches worker-running or turn-running, the child owns the
+        // job state and the parent's close listener must not race with it.
+        return current.phase === "worker-spawned" || current.phase === "queued";
+    });
+}
+async function persistBackgroundFailure(paths, jobId, classified, failedSummary, event, shouldMark = () => true) {
+    let lastWriteError;
+    for (let attempt = 0; attempt <= FAILURE_PERSIST_RETRY_DELAYS_MS.length; attempt += 1) {
+        let store;
+        try {
+            store = new JobStore(paths);
+            const current = store.getJob(jobId);
+            if (!current || current.status !== "running" || !shouldMark(current)) {
+                return;
+            }
+            await markJobFailed(store, paths, current, classified, failedSummary, { phase: "failed" });
+            return;
+        }
+        catch (writeError) {
+            lastWriteError = writeError;
+            if (attempt < FAILURE_PERSIST_RETRY_DELAYS_MS.length) {
+                await sleep(FAILURE_PERSIST_RETRY_DELAYS_MS[attempt]);
+            }
+        }
+        finally {
+            try {
+                store?.close();
+            }
+            catch {
+                // The persistence attempt outcome above is the signal that matters.
+            }
+        }
+    }
+    await appendStuckJobTelemetry(paths, {
+        event,
+        job_id: jobId,
+        failed_summary: failedSummary,
+        error: {
+            code: classified.code,
+            stage: classified.stage,
+            message: classified.message,
+            details: classified.details,
+        },
+        persistence_error: formatError(lastWriteError),
+    });
+}
+async function appendStuckJobTelemetry(paths, entry) {
+    const stuckPath = path.join(paths.pluginRoot, "stuck-jobs.jsonl");
+    try {
+        await appendFile(stuckPath, `${JSON.stringify({ ts: new Date().toISOString(), ...entry })}\n`, "utf8");
+    }
+    catch (appendError) {
+        process.stderr.write(`[kimi-plugin-cc] failed to append stuck job telemetry at ${stuckPath}: ${formatError(appendError)}\n`);
+    }
+}
+function sleep(ms) {
+    return new Promise((resolve) => {
+        setTimeout(resolve, ms);
+    });
+}
+/**
+ * Builds a descriptive message for the rare edge case where `waitForTerminalJob`
+ * returns a terminal job whose `final_output_path` is null (e.g. `markJobFailed`'s
+ * own artifact write failed). The normal background --wait failure path returns
+ * the rendered failure artifact via `readArtifact` — that artifact already
+ * carries the code, stage, and message via `renderTerminalJobArtifact`. This
+ * helper is belt-and-suspenders for the near-unreachable case where even the
+ * failure artifact could not be written. Intended for terminal job records only;
+ * a running record would render the generic "finished without a rendered result."
+ * sentence, which would be misleading.
+ */
+export function describeMissingResult(job, workerKind = "rescue") {
+    const base = `Background ${workerKind} job ${job.job_id} finished without a rendered result`;
+    if (job.status === "failed" || job.status === "cancelled") {
+        const code = job.error?.code || "unknown";
+        const stage = job.error?.stage || "unknown";
+        // `||` (not `??`) intentionally: empty-string error.message or summary
+        // should fall through to the next fallback, not render as blank.
+        const detail = job.error?.message || job.summary || "no further detail";
+        return `${base} (${job.status}, ${code}, stage ${stage}): ${detail}`;
+    }
+    return `${base}.`;
+}

package/plugins/kimi-codex/dist/cli-cancellation.js

@@ -0,0 +1,43 @@
+import process from "node:process";
+export function createCliCancellationHandlers() {
+    const controller = new AbortController();
+    let cancelling = false;
+    let disposed = false;
+    const onSignal = () => {
+        if (cancelling)
+            return;
+        cancelling = true;
+        // Abort BEFORE running through dispose — the cli-client may still be
+        // in its pre-spawn signal check or its post-spawn wait, both of which
+        // honor signal.aborted.
+        try {
+            controller.abort();
+        }
+        catch {
+            // AbortController.abort() can't throw in standard runtimes, but
+            // belt-and-suspenders for runtime quirks (e.g. test harnesses
+            // overriding global AbortController).
+        }
+    };
+    // Use `process.on` (not `once`) so dispose() can remove the listener
+    // via the function reference. `process.once` wraps the callback
+    // internally and depending on Node version removeListener may miss it.
+    // Idempotency comes from the `if (cancelling) return` guard.
+    process.on("SIGTERM", onSignal);
+    process.on("SIGINT", onSignal);
+    return {
+        get cancelling() {
+            return cancelling;
+        },
+        get signal() {
+            return controller.signal;
+        },
+        dispose() {
+            if (disposed)
+                return;
+            disposed = true;
+            process.off("SIGTERM", onSignal);
+            process.off("SIGINT", onSignal);
+        },
+    };
+}