You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
mcpx: TestNoPackageRedeclaresADefault red on clean main — execsvc/progspec constants bypass defaults.json #3085
mcpx: TestNoPackageRedeclaresADefault red on clean main — execsvc/progspec constants bypass defaults.json
Evidence (queue task 4303 diagnosis of PR #2888's mcpx-test unit job, run 41167114746, job 124436952405)
TestNoPackageRedeclaresADefault (internal/settings guard) fails on current main:
guard_test.go:138: constants belong in internal/defaults/defaults.json and, where a user could conceivably want them changed, in the settings registry:
internal/execsvc/hooks.go:63: const hookTimeout = 60 * time.Second
internal/progspec/progspec.go:232: cmd.WaitDelay = 2 * time.Second
internal/progspec/progspec.go:41: const DefaultTimeout = 3 * time.Minute
This is one of the 10 top-level unit failures that make PR #2888's mcpx-test ci-ok red (#1998). The sibling settings-guard failures in the same run are already tracked (#2846: ScriptEnv declarations + env doc + TESTING.md compendium + model.* effect probes; #2697; conformance #2695/#2716; e2e/examples destructive-confirm cluster #2896) — this defaults-guard failure has no dedicated issue.
Acceptance criteria
The three constants are declared in internal/defaults/defaults.json (and in the settings registry where user-tunable) and read from there; no package-level redeclaration remains.
go test ./internal/settings/ -run TestNoPackageRedeclaresADefault passes on clean main.
Related: parent diagnosis #1998 / PR #2888 (this is one of its 10 clean-main unit failures); sibling guard failures already tracked in #2846, #2697, #2695/#2716, and the e2e cluster in #2896 — this defaults-guard failure was the untracked remainder. Notes: Verified live at intake: no merged PR moves these constants yet; the three sites are named with file:line in the body. Failure is on clean main, so this also reddens unrelated PRs that run the settings guard. Risks: Low — behavior-preserving move; the acceptance criteria pin the effective values (60s / 2s / 3m). Suggested approach: Declare the three constants in internal/defaults/defaults.json, register the user-tunable one(s) in the settings registry, read from there, and confirm TestNoPackageRedeclaresADefault passes in CI.
Activity
dezren39 commentedon Oct 31, 2026
Intake review
🤖 Agent note · filed
Related: parent diagnosis #1998 / PR #2888 (this is one of its 10 clean-main unit failures); sibling guard failures already tracked in #2846, #2697, #2695/#2716, and the e2e cluster in #2896 — this defaults-guard failure was the untracked remainder.
Notes: Verified live at intake: no merged PR moves these constants yet; the three sites are named with file:line in the body. Failure is on clean main, so this also reddens unrelated PRs that run the settings guard.
Risks: Low — behavior-preserving move; the acceptance criteria pin the effective values (60s / 2s / 3m).
Suggested approach: Declare the three constants in
internal/defaults/defaults.json, register the user-tunable one(s) in the settings registry, read from there, and confirmTestNoPackageRedeclaresADefaultpasses in CI.dezren39 commentedon Nov 3, 2026
agent-note:v1
task: 6692
lane: code-l
transition: picked_up
state: Task 6692 claimed by lane code-l (direct execution). Implementing the scoped fix: move hookTimeout, cmd.WaitDelay and DefaultTimeout declarations to the defaults source/registry so TestNoPackageRedeclaresADefault passes, keeping effective defaults unchanged (60s / 2s / 3m). Fresh check: issue #3085 OPEN, no hard-stop labels, no existing PR owns this work.
3 remaining items
dezren39 commentedon Nov 3, 2026
🤖 Agent note · picked up
Merge pull request #4719 from developing-today/queue/6692-3085-mcpx-d…
dezren39 commentedon Nov 3, 2026
🤖 Agent note · done