mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
3fc35c91ff
git mv per the regrouping RFC: the five human-collaboration seams and tui join packages/interaction/, app-boot becomes packages/boot/, and jsonrpc joins the renamed scaffold/ (formerly sdk/) as its server half beside client/protocol/create-sdk/helper/scripts/telemetry, whose folders drop the legacy sdk- prefix. Three new group README triplets replace the ui/ and sdk/ ones; tsconfig references/paths/globs, knip keys, vitest globs, gate scripts, catalogs, docs, and the lockfile follow. Adds the four settled FIXME rename markers (dsh-sdk-server, dsh-sdk-telemetry, dsh-sdk-helper, dsh-sdk-scripts). The scaffold folders diverge from their npm names until those renames land, so tsconfig.base.json maps the three affected names explicitly beside the group wildcard. Also repairs two pre-existing stale-path classes the strengthened sweep surfaced: docs/web-styling.md's retired web-ui host package and type-model spec fixture-literal joins. app-boot's three Loader-composition specs time out at the default 5s under full-suite parallel load on this filesystem (pre-existing; pass isolated with --testTimeout=30000); interaction/scaffold/boot suites otherwise green (687 passed).
70 lines
3.2 KiB
TypeScript
70 lines
3.2 KiB
TypeScript
import { availableParallelism } from 'node:os'
|
|
import tsconfigPaths from 'vite-tsconfig-paths'
|
|
import { defineConfig } from 'vitest/config'
|
|
import { standardDecoratorPlugin, vitestExecArgv } from './vitest.shared.ts'
|
|
|
|
const DEFAULT_SNAPSHOT_MAX_CONCURRENCY = 5
|
|
|
|
function positiveIntFromEnv(name: string, fallback: number): number {
|
|
const raw = process.env[name]
|
|
if (raw === undefined || raw === '') return fallback
|
|
|
|
const value = Number(raw)
|
|
if (!Number.isInteger(value) || value < 1) {
|
|
throw new Error(`${name} must be a positive integer, got ${JSON.stringify(raw)}`)
|
|
}
|
|
return value
|
|
}
|
|
|
|
const snapshotMaxConcurrency = positiveIntFromEnv(
|
|
'DSH_SNAPSHOT_MAX_CONCURRENCY',
|
|
Math.min(DEFAULT_SNAPSHOT_MAX_CONCURRENCY, availableParallelism()),
|
|
)
|
|
|
|
// Replay is the keyless default: boot real subprocess paths from recorded model responses and diff
|
|
// assembled requests, normalized protocol or transcript output, and persisted-log expected outputs.
|
|
// `record` calls the real API and updates fixtures and expected outputs; `refresh` replays committed scripts
|
|
// and updates current expected outputs. Replay/refresh never load `.env`; only record reads a key from the
|
|
// environment or root `.env`.
|
|
if (process.env.DSH_SNAPSHOT === 'record') {
|
|
try {
|
|
process.loadEnvFile(new URL('.env', import.meta.url).pathname)
|
|
} catch (error) {
|
|
// ENOENT (no .env) is fine — the key may already be in the environment.
|
|
// Surface any other failure rather than silently recording with wrong env.
|
|
if ((error as NodeJS.ErrnoException | null)?.code !== 'ENOENT') throw error
|
|
}
|
|
}
|
|
|
|
export default defineConfig({
|
|
// Same resolution note as vitest.config.ts: bare workspace names resolve
|
|
// through the tsconfig.base.json paths facade; the native option cannot do
|
|
// this (the root tsconfig is a solution file with no paths).
|
|
plugins: [tsconfigPaths({ projects: ['./tsconfig.base.json'] }), standardDecoratorPlugin()],
|
|
test: {
|
|
execArgv: vitestExecArgv,
|
|
setupFiles: ['./scripts/test-invariants.ts'],
|
|
include: [
|
|
'scripts/**/*.snapshot.ts',
|
|
// The assembled Web snapshot executes generated client bundles; source
|
|
// mode remains the zero-build path, while lib mode requires a prior build.
|
|
...(process.env.DSH_EXAMPLE_MODE === 'lib' ? ['apps/web/tests/**/*.snapshot.ts'] : []),
|
|
'apps/cli/tests/**/*.snapshot.ts',
|
|
'examples/*/tests/**/*.snapshot.ts',
|
|
'packages/scaffold/*/tests/**/*.snapshot.ts',
|
|
],
|
|
// Replay never writes committed outputs and every scenario owns its
|
|
// mutable runtime state (the subprocess suites use a unique temp dir and
|
|
// fixture set per scenario), so replay runs the snapshot files in
|
|
// parallel and bounds in-file concurrency with the environment knob
|
|
// (value 1 restores fully serial replay on constrained machines). Record
|
|
// and refresh stay serial: record spends real API quota per scenario, and
|
|
// refresh write-back harvests volatile values from fixtures already on
|
|
// disk, so concurrent writers would corrupt goldens.
|
|
testTimeout: 120_000,
|
|
hookTimeout: 30_000,
|
|
fileParallelism: (process.env.DSH_SNAPSHOT || 'replay') === 'replay' && snapshotMaxConcurrency > 1,
|
|
maxConcurrency: snapshotMaxConcurrency,
|
|
},
|
|
})
|