mirror of
https://github.com/MoonshotAI/kimi-code.git
synced 2026-07-30 03:24:59 +00:00
1d7c205e83
Some checks are pending
CI / test-pi-tui (push) Waiting to run
CI / test-windows (push) Waiting to run
CI / lint (push) Waiting to run
CI / build (push) Waiting to run
CI / test (1) (push) Waiting to run
CI / test (2) (push) Waiting to run
CI / test (3) (push) Waiting to run
CI / test (4) (push) Waiting to run
CI / test (5) (push) Waiting to run
Nix Build / Check flake.nix workspace sync (push) Waiting to run
Nix Build / nix build .#kimi-code (push) Blocked by required conditions
Release / Release (push) Waiting to run
Release / Deploy docs (push) Blocked by required conditions
CI / typecheck (push) Waiting to run
Release / Native release artifact (push) Blocked by required conditions
Release / Desktop release artifact (push) Blocked by required conditions
Release / Publish native release assets (push) Blocked by required conditions
* fix: record crash telemetry for unhandled promise rejections The crash handler only listened on uncaughtExceptionMonitor, which never fires for a rejection that has a listener — and the TUI always registers one, converting rejections into a silent exit(1) with no telemetry at all. Observe unhandledRejection directly so those crashes still leave a trace. Since registering a real listener suppresses Node's default crash-on-rejection, rethrow when we are the only listener (print / server modes), deduped so the monitor does not double-report. * fix: fall back to text paste when the clipboard image handler rejects The Ctrl+V image-paste dispatch chained off the async handler without a rejection branch, so any failure inside it became an unhandled rejection — which the CLI's crash path turns into a silent exit(1). Treat a rejection like "no image available" and paste as text. * fix: dedupe all rethrown rejection reasons at the crash monitor Non-Error rejection reasons (plain objects, strings, null) were recorded by the rejection handler but not added to the dedupe set, so the uncaughtExceptionMonitor pass after the rethrow reported a second crash for the same failure; null/undefined reasons also crashed the monitor's own error-type extraction. Use a Set so primitives dedupe by value, add every rethrown reason, and classify monitor crashes null-safely. |
||
|---|---|---|
| .. | ||
| src | ||
| test | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| tsdown.config.ts | ||
| vitest.config.ts | ||