chore: import upstream snapshot with attribution

2026-07-13 13:39:12 +08:00
commit d8dcd5f6d1
8604 changed files with 2479390 additions and 0 deletions
@@ -0,0 +1,48 @@
+// Test-only DATA_DIR isolation.
+//
+// Loaded via `node --import ./tests/_setup/isolateDataDir.ts` from the test/mutation
+// invocations (package.json test scripts, stryker.conf.json tap.nodeArgs, the
+// quality.yml TIA step, and the CI test jobs) — NEVER from production. It MUST stay
+// out of open-sse/utils/setupPolyfill.ts, which is also imported by production
+// (bin/omniroute.mjs, proxyFetch.ts, proxyDispatcher.ts) where redirecting DATA_DIR
+// would point the live SQLite DB at a throwaway temp dir.
+//
+// Why: node:test spawns a process per test file and Stryker spawns one per sandbox,
+// but every process resolves DATA_DIR to the SAME default (~/.omniroute) when the env
+// var is unset (see src/lib/dataPaths.ts::resolveDataDir). Concurrent processes then
+// open the SAME on-disk storage.sqlite, causing cross-file state races: SQLite lock
+// contention that hangs `test:unit` under high `--test-concurrency`, and the
+// non-deterministic baseline that forced Stryker to `concurrency: 1`.
+//
+// Giving each process its own DATA_DIR under the OS temp dir removes the shared file,
+// so concurrent test processes never collide. Tests that set DATA_DIR explicitly keep
+// winning — this only fills in an isolated default when none was chosen.
+import fs from "node:fs";
+import os from "node:os";
+import path from "node:path";
+
+// File logger worker threads can outlive a test's temporary DATA_DIR cleanup and then
+// raise ENOENT/ENOTEMPTY after the test has already passed. Keep the global test default
+// console-only; tests that cover file logging explicitly set APP_LOG_TO_FILE themselves.
+process.env.APP_LOG_TO_FILE ||= "false";
+
+if (!process.env.DATA_DIR) {
+  const dir = fs.mkdtempSync(path.join(os.tmpdir(), "omniroute-test-"));
+  process.env.DATA_DIR = dir;
+
+  // Best-effort cleanup so a long suite run does not leak hundreds of temp DBs.
+  process.on("exit", () => {
+    try {
+      fs.rmSync(dir, { recursive: true, force: true });
+    } catch {
+      // ignore — the OS reaps its temp dir eventually.
+    }
+  });
+}
+
+// System-trust guard: the suite must NEVER mutate the OS trust store. On a
+// persistent self-hosted runner the cert-flow integration test installed a fake
+// 105-byte PEM into /usr/local/share/ca-certificates and update-ca-certificates
+// baked it into the bundle, breaking ALL system TLS on the VM (2026-07-05).
+// installCert/uninstallCert/installTproxyCa/uninstallTproxyCa no-op under this.
+process.env.OMNIROUTE_SKIP_SYSTEM_TRUST = "1";