mirror of
https://github.com/stablyai/orca.git
synced 2026-09-22 16:02:32 +00:00
* chore(lint): upgrade oxlint to 1.71 and enable 7 new rules Upgrade oxlint 1.67.0 -> 1.71.0 (1.72 was blocked by the repo's 3-day minimum-release-age supply-chain guard; nothing here needs it). The bump is a no-op on the existing config. Enable 3 error rules (backlog autofixed to zero in this commit) and 4 warn rules (surface signal without gating CI): error (autofixed, behavior-preserving): - unicorn/prefer-node-protocol (~1531 sites: bare builtin -> node:) - typescript/no-import-type-side-effects (~36: all-inline-type -> import type) - unicorn/no-array-reverse (19: copy-then-reverse -> toReversed) warn (real signal, current fires are test-only/correct): - unicorn/no-array-fill-with-reference-type (aliasing footgun guard) - typescript/no-unsafe-function-type (bans bare Function type) - unicorn/prefer-array-flat-map (map().flat() -> flatMap()) - unicorn/prefer-regexp-test (.match() in bool ctx -> .test()) mobile/.oxlintrc.json extends root, so it inherits all 7; the autofix ran from root and covered mobile/ too. Verification (all green): oxlint 0 errors (root+mobile+aux configs), oxfmt clean, typecheck (node+cli+web), vitest 22795 passed / 0 failed, builds (electron-vite + web + cli) succeed. node: rewrites confirmed to skip embedded SSH/CLI string payloads (AST-only); all toReversed sites verified to operate on fresh copies or write-once locals. * chore(lint): bump mobile oxlint to 1.71 so inherited rules parse mobile/ is a standalone pnpm project pinning its own oxlint@1.67, which lacks unicorn/no-array-fill-with-reference-type (needs >=1.70). Since mobile/.oxlintrc.json extends the root config, mobile CI's 'cd mobile && oxlint' failed to parse the new rule. Bump mobile to match root (1.71). Verified in mobile/: oxlint 0 errors, oxfmt --check clean, tsc --noEmit pass, vitest 978 passed / 0 failed. Co-authored-by: Orca <help@stably.ai> --------- Co-authored-by: Orca <help@stably.ai>
109 lines
3.8 KiB
TypeScript
109 lines
3.8 KiB
TypeScript
import { execFile as execFileCb } from 'node:child_process'
|
|
import { promisify } from 'node:util'
|
|
|
|
const execFile = promisify(execFileCb)
|
|
|
|
// Why: agent foreground-process inspection runs this full process-table scan on
|
|
// a 750ms/2000ms per-pane cadence. On a shared SSH relay every tracked agent
|
|
// terminal drives it, so concurrent panes used to each fork their own `ps`,
|
|
// pinning idle CPU (issue #6288). Memoizing collapses overlapping scans to one.
|
|
const PS_ARGS = ['-axo', 'pid=,ppid=,stat=,command='] as const
|
|
const PS_TIMEOUT_MS = 3000
|
|
|
|
// Why: 500ms is below the active cadence poll's minimum inter-poll gap (~675ms
|
|
// = 750ms less jitter), so a cadence-driven pane never reuses a snapshot older
|
|
// than it would have scanned itself; a burst of panes polling in the same
|
|
// window collapses from up to 8 scans/sec down to ~2/sec. The faster
|
|
// event-driven follow-up inspections (e.g. the pending-title confirmation,
|
|
// which can re-fire <500ms apart) intentionally accept a <=500ms-stale table:
|
|
// they only confirm the same agent still owns the pane, and process-exit is
|
|
// debounced across repeated samples, so a near-instant cached scan answers
|
|
// identically to a fresh fork.
|
|
const DEFAULT_SNAPSHOT_TTL_MS = 500
|
|
|
|
type Snapshot = { stdout: string; capturedAtMs: number }
|
|
|
|
type ProcessTableSnapshotReaderDeps = {
|
|
runPs: () => Promise<string>
|
|
now: () => number
|
|
ttlMs?: number
|
|
}
|
|
|
|
/**
|
|
* Build a process-table snapshot reader that deduplicates concurrent and
|
|
* near-simultaneous `ps` scans behind a single in-flight promise + short TTL.
|
|
* Exposed as a factory so tests can inject the scan and clock; production code
|
|
* uses the shared `getProcessTableSnapshot` instance below.
|
|
*/
|
|
export function createProcessTableSnapshotReader(deps: ProcessTableSnapshotReaderDeps): {
|
|
getSnapshot: () => Promise<string>
|
|
reset: () => void
|
|
} {
|
|
const ttlMs = deps.ttlMs ?? DEFAULT_SNAPSHOT_TTL_MS
|
|
let cached: Snapshot | null = null
|
|
let inFlight: Promise<string> | null = null
|
|
|
|
async function getSnapshot(): Promise<string> {
|
|
if (cached && deps.now() - cached.capturedAtMs < ttlMs) {
|
|
return cached.stdout
|
|
}
|
|
if (inFlight) {
|
|
return inFlight
|
|
}
|
|
const promise = deps.runPs()
|
|
inFlight = promise
|
|
try {
|
|
const stdout = await promise
|
|
// Why: stamp capture time AFTER the scan returns so a slow `ps` can't
|
|
// hand back a snapshot that is already older than its TTL.
|
|
cached = { stdout, capturedAtMs: deps.now() }
|
|
return stdout
|
|
} finally {
|
|
// Clear in-flight on success and failure so a transient `ps` error
|
|
// (timeout, nonzero exit) retries on the next call instead of being
|
|
// cached; callers keep their existing best-effort fall-through.
|
|
if (inFlight === promise) {
|
|
inFlight = null
|
|
}
|
|
}
|
|
}
|
|
|
|
return {
|
|
getSnapshot,
|
|
// Why: lets tests that mock `ps` per case clear the cross-call cache so one
|
|
// case's snapshot can't satisfy the next within the TTL window.
|
|
reset: () => {
|
|
cached = null
|
|
inFlight = null
|
|
}
|
|
}
|
|
}
|
|
|
|
const defaultReader = createProcessTableSnapshotReader({
|
|
runPs: async () => {
|
|
const { stdout } = await execFile('ps', [...PS_ARGS], {
|
|
encoding: 'utf-8',
|
|
timeout: PS_TIMEOUT_MS
|
|
})
|
|
return stdout
|
|
},
|
|
now: () => Date.now()
|
|
})
|
|
|
|
/**
|
|
* Run (or reuse a recent) `ps -axo pid=,ppid=,stat=,command=` scan and return
|
|
* its raw stdout. Per-process singleton: the relay and local main processes
|
|
* each dedupe their own scans.
|
|
*/
|
|
export function getProcessTableSnapshot(): Promise<string> {
|
|
return defaultReader.getSnapshot()
|
|
}
|
|
|
|
/**
|
|
* Test-only: clear the shared snapshot cache so suites that mock `ps` between
|
|
* cases don't have one case's snapshot served to the next within the TTL.
|
|
*/
|
|
export function resetProcessTableSnapshotForTests(): void {
|
|
defaultReader.reset()
|
|
}
|