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>
58 lines
1.5 KiB
JavaScript
58 lines
1.5 KiB
JavaScript
"use strict";
|
|
var __importDefault = (this && this.__importDefault) || function (mod) {
|
|
return (mod && mod.__esModule) ? mod : { "default": mod };
|
|
};
|
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
exports.allSignals = void 0;
|
|
const node_constants_1 = __importDefault(require("node:constants"));
|
|
exports.allSignals =
|
|
// this is the full list of signals that Node will let us do anything with
|
|
Object.keys(node_constants_1.default).filter(k => k.startsWith('SIG') &&
|
|
// https://github.com/tapjs/signal-exit/issues/21
|
|
k !== 'SIGPROF' &&
|
|
// no sense trying to listen for SIGKILL, it's impossible
|
|
k !== 'SIGKILL');
|
|
// These are some obscure signals that are reported by kill -l
|
|
// on macOS, Linux, or Windows, but which don't have any mapping
|
|
// in Node.js. No sense trying if they're just going to throw
|
|
// every time on every platform.
|
|
//
|
|
// 'SIGEMT',
|
|
// 'SIGLOST',
|
|
// 'SIGPOLL',
|
|
// 'SIGRTMAX',
|
|
// 'SIGRTMAX-1',
|
|
// 'SIGRTMAX-10',
|
|
// 'SIGRTMAX-11',
|
|
// 'SIGRTMAX-12',
|
|
// 'SIGRTMAX-13',
|
|
// 'SIGRTMAX-14',
|
|
// 'SIGRTMAX-15',
|
|
// 'SIGRTMAX-2',
|
|
// 'SIGRTMAX-3',
|
|
// 'SIGRTMAX-4',
|
|
// 'SIGRTMAX-5',
|
|
// 'SIGRTMAX-6',
|
|
// 'SIGRTMAX-7',
|
|
// 'SIGRTMAX-8',
|
|
// 'SIGRTMAX-9',
|
|
// 'SIGRTMIN',
|
|
// 'SIGRTMIN+1',
|
|
// 'SIGRTMIN+10',
|
|
// 'SIGRTMIN+11',
|
|
// 'SIGRTMIN+12',
|
|
// 'SIGRTMIN+13',
|
|
// 'SIGRTMIN+14',
|
|
// 'SIGRTMIN+15',
|
|
// 'SIGRTMIN+16',
|
|
// 'SIGRTMIN+2',
|
|
// 'SIGRTMIN+3',
|
|
// 'SIGRTMIN+4',
|
|
// 'SIGRTMIN+5',
|
|
// 'SIGRTMIN+6',
|
|
// 'SIGRTMIN+7',
|
|
// 'SIGRTMIN+8',
|
|
// 'SIGRTMIN+9',
|
|
// 'SIGSTKFLT',
|
|
// 'SIGUNUSED',
|
|
//# sourceMappingURL=all-signals.js.map
|