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> |
||
|---|---|---|
| .. | ||
| dist | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
agent-base
Turn a function into an http.Agent instance
This module is a thin wrapper around the base http.Agent class.
It provides an abstract class that must define a connect() function,
which is responsible for creating the underlying socket that the HTTP
client requests will use.
The connect() function may return an arbitrary Duplex stream, or
another http.Agent instance to delegate the request to, and may be
asynchronous (by defining an async function).
Instances of this agent can be used with the http and https
modules. To differentiate, the options parameter in the connect()
function includes a secureEndpoint property, which can be checked
to determine what type of socket should be returned.
Some subclasses:
Here are some more interesting uses of agent-base.
Send a pull request to list yours!
http-proxy-agent: An HTTP(s) proxyhttp.Agentimplementation for HTTP endpointshttps-proxy-agent: An HTTP(s) proxyhttp.Agentimplementation for HTTPS endpointspac-proxy-agent: A PAC file proxyhttp.Agentimplementation for HTTP and HTTPSsocks-proxy-agent: A SOCKS proxyhttp.Agentimplementation for HTTP and HTTPS
Example
Here's a minimal example that creates a new net.Socket or tls.Socket
based on the secureEndpoint property. This agent can be used with both
the http and https modules.
import * as net from 'net';
import * as tls from 'tls';
import * as http from 'http';
import { Agent } from 'agent-base';
class MyAgent extends Agent {
connect(req, opts) {
// `secureEndpoint` is true when using the "https" module
if (opts.secureEndpoint) {
return tls.connect(opts);
} else {
return net.connect(opts);
}
}
});
// Keep alive enabled means that `connect()` will only be
// invoked when a new connection needs to be created
const agent = new MyAgent({ keepAlive: true });
// Pass the `agent` option when creating the HTTP request
http.get('http://nodejs.org/api/', { agent }, (res) => {
console.log('"response" event!', res.headers);
res.pipe(process.stdout);
});