* test(#3148): bound the long tail and delete the allowlist Migrates the final 170 unbounded sync spawn sites across 49 files, then removes the allowlist entirely. local/no-unbounded-spawn now runs with no exemption surface across tests/**: there is no file to add a name to. drift-detection's throw-native git() helper routes to gitOrThrow -- bare runGit would have taken 16 call sites quiet on failure. commands.test.cjs has two independently-scoped runGsdTools/runCli helpers, one already bounded and one not; they are kept distinct rather than unified, the same trap as the two same-named git() helpers in Wave 1. runNpm's bound was erasable. Its options spread callerOptions after the defaults, so an explicit timeout:undefined silently dropped the 180000ms bound -- the rule flagged it and was right; it was not a false positive. Fixed by destructuring with a default, with a test that fails when the default is removed. Two sites stay on a raw spawn with an explicit timeout because the seam cannot express them: one needs shell:true for npm.cmd on Windows, one redirects stdout to a real fd. Both are the rule's own documented second option, not an escape from it. Closure verified rather than asserted: the derivation scan reports 0 unbounded spawn helpers and 0 unbounded direct git call sites, and a temporary file carrying an unbounded spawn still errors with the allowlist gone. Closes #3064. * test(#3148): close a hole in the guard's own eslint-disable ban The ban listed only the top level of tests/, so it was blind to 37 .cjs files under tests/helpers, qa, observability, fixtures and dispatch. With the allowlist deleted this test is the sole remaining way to detect someone silencing the rule inline, so the gap was load-bearing: a nested file could carry an unbounded spawn plus an eslint-disable and pass everything. Proven before and after. A probe planted under tests/helpers with both was invisible to the guard and clean under eslint; after making the listing recursive the guard fails on it. The scanned set goes from 771 files to 808. Pre-existing since the guard shipped, but this wave is what promoted it to sole defense, so it is fixed here rather than filed. Also converts the last hand-rolled throw check to throwIfFailed and the last re-derived legacy shape to compose toLegacyResult, which makes the epic's none-remain claim true rather than nearly true. toLegacyResult itself is not widened -- eight callers depend on its shape and one consumer does not justify changing a shared contract. * fix(#3148): correct seam incoherence at the bound and a slow review-lane error path Two real failures from the remote runner, both fixed at the cause. The seam could return outcome TIMED_OUT together with exitCode 0. At the exact bound spawnSync reports ETIMEDOUT while the child has already exited with a real status, and toSeamResult classified on the error code while passing status straight through -- an incoherent pair its own boundary test was written to catch, and did. A status that is not null is direct evidence the child exited on its own, so it now decides the outcome before the error-code branches run. process-seam.cjs was deliberately untouched by every earlier wave; this is a defect in the module itself, kept surgical, with a unit test that fails against the old logic. review-lane with an unknown subcommand fell through to its usage error only after loading the capability registry and building a per-lane plan, which spawns one child process per lane -- up to twelve. The error path took ~1288ms instead of ~119ms, and under bench load it outran a caller's spawn timeout and was killed before writing anything, which is the empty stdout and stderr CI saw. It now fails fast before any of that work begins. This is the epic's first production change. It is user-facing, so it carries a changeset rather than a no-changelog label. * test(#3148): replace a real-race timeout test with a deterministic one E9 raced git rev-parse against a 1ms bound and assumed git always lost. On a warm container git finishes first, spawnSync returns status 0 with no error at all, the seam correctly classifies EXITED, and gitOrThrow correctly does not throw -- so the test failed on both lanes. A probe confirms a genuine timeout always carries status null, so this was never the seam misbehaving. Raising the bound would only lengthen the odds, which is the same defect with better luck. The test now drives gitOrThrow against a stubbed runGit that returns a synthetic TIMED_OUT result, so it asserts exactly what it always meant to -- that a timeout propagates as a throw -- with no timing dependence. Five consecutive runs are identical where the old one varied. I wrote this test in Wave 0; it is a real-race test by construction and CLAUDE.md says to replace those rather than re-run them. * chore(#3148): backfill changeset PR number 3192 --------- Co-authored-by: sim <sim@local>
122 lines
5.6 KiB
JavaScript
122 lines
5.6 KiB
JavaScript
'use strict';
|
||
|
||
/**
|
||
* #2136 — operator-facing date-only fields must use the HOST-LOCAL calendar day,
|
||
* not the UTC calendar day.
|
||
*
|
||
* `clock.today()` derived the day by slicing a UTC ISO instant
|
||
* (`nowIso().split('T')[0]`), so in any negative-UTC-offset zone during UTC's
|
||
* early hours `last_activity` named a day the operator had not reached yet — a
|
||
* day AHEAD of `last_updated`'s local date, written by the same call.
|
||
*
|
||
* The fix adds `clock.localToday()` (host-local calendar day, honoring the same
|
||
* GSD_NOW_MS pin) and routes operator-facing date-only fields through it. These
|
||
* tests prove:
|
||
* (1) realClock.localToday() returns the local day under a pinned instant + TZ;
|
||
* (2) realClock.today() is unchanged (UTC) — internal/cosmetic stamps stay UTC;
|
||
* (3) the fake clock mirrors localToday();
|
||
* (4) the `last_activity` field is stamped from localToday, not today
|
||
* (a split clock where the two differ proves the wiring).
|
||
*/
|
||
|
||
const { describe, test } = require('node:test');
|
||
const assert = require('node:assert/strict');
|
||
const path = require('node:path');
|
||
|
||
const CLOCK_CJS = path.join(__dirname, '..', 'gsd-core', 'bin', 'lib', 'clock.cjs');
|
||
const STATE_TRANSITION_CJS = path.join(__dirname, '..', 'gsd-core', 'bin', 'lib', 'state-transition.cjs');
|
||
const { stateExtractField } = require('../gsd-core/bin/lib/state-document.cjs');
|
||
const { makeFakeClock } = require('./helpers/clock.cjs');
|
||
const { runNode } = require('./helpers/process-seam.cjs');
|
||
const { throwIfFailed } = require('./helpers/git-fixture.cjs');
|
||
const { PROBE_TIMEOUT_MS } = require('./helpers/timeouts.cjs');
|
||
|
||
// 2020-06-15T02:00:00.000Z. Under America/Chicago (UTC−5 in June) this instant
|
||
// is 2020-06-14 21:00 local — the local calendar day is 2020-06-14 while the UTC
|
||
// calendar day is 2020-06-15. This is the issue's exact repro instant.
|
||
const PINNED_MS = '1592186400000';
|
||
|
||
/**
|
||
* Run a one-liner in a FRESH subprocess so TZ is set at process start (Node
|
||
* caches timezone; runtime mutation of process.env.TZ is unreliable across
|
||
* versions). GSD_TEST_MODE + GSD_NOW_MS pin realClock via the documented seam.
|
||
*/
|
||
function clockInSubprocess(expr, env) {
|
||
const result = runNode(['-e', expr], { env, timeoutMs: PROBE_TIMEOUT_MS });
|
||
throwIfFailed(result, `node -e ${expr}`);
|
||
return result.stdout.trim();
|
||
}
|
||
|
||
describe('#2136 realClock.localToday() — host-local calendar day', () => {
|
||
test('returns the LOCAL calendar day under a negative-UTC-offset zone', () => {
|
||
const out = clockInSubprocess(
|
||
`const {realClock}=require(${JSON.stringify(CLOCK_CJS)});process.stdout.write(realClock.localToday());`,
|
||
{ PATH: process.env.PATH, GSD_TEST_MODE: '1', GSD_NOW_MS: PINNED_MS, TZ: 'America/Chicago' },
|
||
);
|
||
assert.strictEqual(out, '2020-06-14',
|
||
'localToday() must be the local calendar day (2020-06-14 in Chicago), not the UTC day (2020-06-15)');
|
||
});
|
||
|
||
test('realClock.today() is unchanged (UTC calendar day) — internal stamps stay UTC', () => {
|
||
const out = clockInSubprocess(
|
||
`const {realClock}=require(${JSON.stringify(CLOCK_CJS)});process.stdout.write(realClock.today());`,
|
||
{ PATH: process.env.PATH, GSD_TEST_MODE: '1', GSD_NOW_MS: PINNED_MS, TZ: 'America/Chicago' },
|
||
);
|
||
assert.strictEqual(out, '2020-06-15',
|
||
'today() must remain the UTC calendar day; only operator-facing fields moved to localToday()');
|
||
});
|
||
|
||
test('localToday === today on a UTC host (no spurious divergence)', () => {
|
||
const out = clockInSubprocess(
|
||
`const {realClock}=require(${JSON.stringify(CLOCK_CJS)});process.stdout.write(realClock.localToday()+'|'+realClock.today());`,
|
||
{ PATH: process.env.PATH, GSD_TEST_MODE: '1', GSD_NOW_MS: PINNED_MS, TZ: 'UTC' },
|
||
);
|
||
const [local, utc] = out.split('|');
|
||
assert.strictEqual(local, '2020-06-15');
|
||
assert.strictEqual(utc, '2020-06-15');
|
||
});
|
||
});
|
||
|
||
describe('#2136 makeFakeClock mirrors localToday()', () => {
|
||
test('fake clock localToday() derives the local day from the pinned epoch', () => {
|
||
const clock = makeFakeClock(Number(PINNED_MS));
|
||
// The fake honors the host TZ of the test process; assert it returns a
|
||
// YYYY-MM-DD string derived from local Date methods (structure + determinism
|
||
// under the pinned epoch), mirroring realClock.localToday().
|
||
assert.ok(/^\d{4}-\d{2}-\d{2}$/.test(clock.localToday()),
|
||
'fake localToday() must return a YYYY-MM-DD string');
|
||
assert.strictEqual(typeof clock.localToday, 'function',
|
||
'makeFakeClock must expose localToday so it stays a drop-in Clock substitute');
|
||
});
|
||
});
|
||
|
||
describe('#2136 last_activity is stamped from localToday, not today', () => {
|
||
// A clock where the UTC day and the local day DIFFER. If the transition core
|
||
// still consulted today(), Last Activity would read the UTC value; the fix
|
||
// routes it through localToday().
|
||
const splitClock = Object.freeze({
|
||
today: () => '2020-06-15',
|
||
localToday: () => '2020-06-14',
|
||
nowIso: () => '2020-06-15T02:00:00.000Z',
|
||
});
|
||
|
||
test('sync transition writes the LOCAL day into Last Activity', () => {
|
||
const { transitionCore } = require(STATE_TRANSITION_CJS);
|
||
const input = [
|
||
'# Project State',
|
||
'',
|
||
'**Total Plans in Phase:** 2',
|
||
'**Last Activity:** 2020-06-10',
|
||
'**Progress:** [████░░░░░░] 40%',
|
||
'',
|
||
].join('\n');
|
||
const result = transitionCore(
|
||
input,
|
||
{ kind: 'sync', totalPlansInPhase: 5, percent: 60 },
|
||
{ clock: splitClock },
|
||
);
|
||
assert.strictEqual(stateExtractField(result.content, 'Last Activity'), '2020-06-14',
|
||
'Last Activity must use localToday() (2020-06-14), not today() (2020-06-15)');
|
||
});
|
||
});
|