8839075805
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>
34 lines
1.6 KiB
JavaScript
34 lines
1.6 KiB
JavaScript
import {getFdSpecificValue} from '../arguments/specific.js';
|
|
|
|
// The `verbose` option can have different values for `stdout`/`stderr`
|
|
export const isVerbose = ({verbose}, fdNumber) => getFdVerbose(verbose, fdNumber) !== 'none';
|
|
|
|
// Whether IPC and output and logged
|
|
export const isFullVerbose = ({verbose}, fdNumber) => !['none', 'short'].includes(getFdVerbose(verbose, fdNumber));
|
|
|
|
// The `verbose` option can be a function to customize logging
|
|
export const getVerboseFunction = ({verbose}, fdNumber) => {
|
|
const fdVerbose = getFdVerbose(verbose, fdNumber);
|
|
return isVerboseFunction(fdVerbose) ? fdVerbose : undefined;
|
|
};
|
|
|
|
// When using `verbose: {stdout, stderr, fd3, ipc}`:
|
|
// - `verbose.stdout|stderr|fd3` is used for 'output'
|
|
// - `verbose.ipc` is only used for 'ipc'
|
|
// - highest `verbose.*` value is used for 'command', 'error' and 'duration'
|
|
const getFdVerbose = (verbose, fdNumber) => fdNumber === undefined
|
|
? getFdGenericVerbose(verbose)
|
|
: getFdSpecificValue(verbose, fdNumber);
|
|
|
|
// When using `verbose: {stdout, stderr, fd3, ipc}` and logging is not specific to a file descriptor.
|
|
// We then use the highest `verbose.*` value, using the following order:
|
|
// - function > 'full' > 'short' > 'none'
|
|
// - if several functions are defined: stdout > stderr > fd3 > ipc
|
|
const getFdGenericVerbose = verbose => verbose.find(fdVerbose => isVerboseFunction(fdVerbose))
|
|
?? VERBOSE_VALUES.findLast(fdVerbose => verbose.includes(fdVerbose));
|
|
|
|
// Whether the `verbose` option is customized using a function
|
|
export const isVerboseFunction = fdVerbose => typeof fdVerbose === 'function';
|
|
|
|
export const VERBOSE_VALUES = ['none', 'short', 'full'];
|