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>
42 lines
1.0 KiB
Markdown
42 lines
1.0 KiB
Markdown
# get-caller-file
|
|
|
|
[](https://travis-ci.org/stefanpenner/get-caller-file)
|
|
[](https://ci.appveyor.com/project/embercli/get-caller-file/branch/master)
|
|
|
|
This is a utility, which allows a function to figure out from which file it was invoked. It does so by inspecting v8's stack trace at the time it is invoked.
|
|
|
|
Inspired by http://stackoverflow.com/questions/13227489
|
|
|
|
*note: this relies on Node/V8 specific APIs, as such other runtimes may not work*
|
|
|
|
## Installation
|
|
|
|
```bash
|
|
yarn add get-caller-file
|
|
```
|
|
|
|
## Usage
|
|
|
|
Given:
|
|
|
|
```js
|
|
// ./foo.js
|
|
const getCallerFile = require('get-caller-file');
|
|
|
|
module.exports = function() {
|
|
return getCallerFile(); // figures out who called it
|
|
};
|
|
```
|
|
|
|
```js
|
|
// index.js
|
|
const foo = require('./foo');
|
|
|
|
foo() // => /full/path/to/this/file/index.js
|
|
```
|
|
|
|
|
|
## Options:
|
|
|
|
* `getCallerFile(position = 2)`: where position is stack frame whos fileName we want.
|