Implements Phases 1-8 of the TFTSR implementation plan. Rust backend (Tauri 2.x, src-tauri/): - Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama - PII detection engine: 11 regex patterns with overlap resolution - SQLCipher AES-256 encrypted database with 10 versioned migrations - 28 Tauri IPC commands for triage, analysis, document, and system ops - Ollama: hardware probe, model recommendations, pull/delete with events - RCA and blameless post-mortem Markdown document generators - PDF export via printpdf - Audit log: SHA-256 hash of every external data send - Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2) Frontend (React 18 + TypeScript + Vite, src/): - 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings - 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives - 3 Zustand stores: session, settings (persisted), history - Type-safe tauriCommands.ts matching Rust backend types exactly - 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs) DevOps: - .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push - .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload Verified: - cargo check: zero errors - tsc --noEmit: zero errors - vitest run: 13/13 unit tests passing Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
55 lines
1.8 KiB
JavaScript
55 lines
1.8 KiB
JavaScript
import {once} from 'node:events';
|
|
import {DiscardedError} from '../return/final-error.js';
|
|
|
|
// If `error` is emitted before `spawn`, `exit` will never be emitted.
|
|
// However, `error` might be emitted after `spawn`.
|
|
// In that case, `exit` will still be emitted.
|
|
// Since the `exit` event contains the signal name, we want to make sure we are listening for it.
|
|
// This function also takes into account the following unlikely cases:
|
|
// - `exit` being emitted in the same microtask as `spawn`
|
|
// - `error` being emitted multiple times
|
|
export const waitForExit = async (subprocess, context) => {
|
|
const [exitCode, signal] = await waitForExitOrError(subprocess);
|
|
context.isForcefullyTerminated ??= false;
|
|
return [exitCode, signal];
|
|
};
|
|
|
|
const waitForExitOrError = async subprocess => {
|
|
const [spawnPayload, exitPayload] = await Promise.allSettled([
|
|
once(subprocess, 'spawn'),
|
|
once(subprocess, 'exit'),
|
|
]);
|
|
|
|
if (spawnPayload.status === 'rejected') {
|
|
return [];
|
|
}
|
|
|
|
return exitPayload.status === 'rejected'
|
|
? waitForSubprocessExit(subprocess)
|
|
: exitPayload.value;
|
|
};
|
|
|
|
const waitForSubprocessExit = async subprocess => {
|
|
try {
|
|
return await once(subprocess, 'exit');
|
|
} catch {
|
|
return waitForSubprocessExit(subprocess);
|
|
}
|
|
};
|
|
|
|
// Retrieve the final exit code and|or signal name
|
|
export const waitForSuccessfulExit = async exitPromise => {
|
|
const [exitCode, signal] = await exitPromise;
|
|
|
|
if (!isSubprocessErrorExit(exitCode, signal) && isFailedExit(exitCode, signal)) {
|
|
throw new DiscardedError();
|
|
}
|
|
|
|
return [exitCode, signal];
|
|
};
|
|
|
|
// When the subprocess fails due to an `error` event
|
|
const isSubprocessErrorExit = (exitCode, signal) => exitCode === undefined && signal === undefined;
|
|
// When the subprocess fails due to a non-0 exit code or to a signal termination
|
|
export const isFailedExit = (exitCode, signal) => exitCode !== 0 || signal !== null;
|