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
2.0 KiB
JavaScript
55 lines
2.0 KiB
JavaScript
import {inspect} from 'node:util';
|
|
import {escapeLines} from '../arguments/escape.js';
|
|
import {defaultVerboseFunction} from './default.js';
|
|
import {applyVerboseOnLines} from './custom.js';
|
|
|
|
// This prints on stderr.
|
|
// If the subprocess prints on stdout and is using `stdout: 'inherit'`,
|
|
// there is a chance both writes will compete (introducing a race condition).
|
|
// This means their respective order is not deterministic.
|
|
// In particular, this means the verbose command lines might be after the start of the subprocess output.
|
|
// Using synchronous I/O does not solve this problem.
|
|
// However, this only seems to happen when the stdout/stderr target
|
|
// (e.g. a terminal) is being written to by many subprocesses at once, which is unlikely in real scenarios.
|
|
export const verboseLog = ({type, verboseMessage, fdNumber, verboseInfo, result}) => {
|
|
const verboseObject = getVerboseObject({type, result, verboseInfo});
|
|
const printedLines = getPrintedLines(verboseMessage, verboseObject);
|
|
const finalLines = applyVerboseOnLines(printedLines, verboseInfo, fdNumber);
|
|
if (finalLines !== '') {
|
|
console.warn(finalLines.slice(0, -1));
|
|
}
|
|
};
|
|
|
|
const getVerboseObject = ({
|
|
type,
|
|
result,
|
|
verboseInfo: {escapedCommand, commandId, rawOptions: {piped = false, ...options}},
|
|
}) => ({
|
|
type,
|
|
escapedCommand,
|
|
commandId: `${commandId}`,
|
|
timestamp: new Date(),
|
|
piped,
|
|
result,
|
|
options,
|
|
});
|
|
|
|
const getPrintedLines = (verboseMessage, verboseObject) => verboseMessage
|
|
.split('\n')
|
|
.map(message => getPrintedLine({...verboseObject, message}));
|
|
|
|
const getPrintedLine = verboseObject => {
|
|
const verboseLine = defaultVerboseFunction(verboseObject);
|
|
return {verboseLine, verboseObject};
|
|
};
|
|
|
|
// Serialize any type to a line string, for logging
|
|
export const serializeVerboseMessage = message => {
|
|
const messageString = typeof message === 'string' ? message : inspect(message);
|
|
const escapedMessage = escapeLines(messageString);
|
|
return escapedMessage.replaceAll('\t', ' '.repeat(TAB_SIZE));
|
|
};
|
|
|
|
// Same as `util.inspect()`
|
|
const TAB_SIZE = 2;
|