Skip to content

fix(dispatch): make launcher-command test hermetic to ambient SPACEDOCK_BIN#340

Merged
clkao merged 1 commit into
nextfrom
fix/dispatch-launcher-test-hermeticity
Jun 9, 2026
Merged

fix(dispatch): make launcher-command test hermetic to ambient SPACEDOCK_BIN#340
clkao merged 1 commit into
nextfrom
fix/dispatch-launcher-test-hermeticity

Conversation

@clkao

@clkao clkao commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Makes the dispatch launcher-command test hermetic to an ambient SPACEDOCK_BIN, so it passes under a spacedock claude/codex session (which exports one) as well as in CI.

What changed

  • Strip SPACEDOCK_BIN from the inherited environment in runLauncherCommand so each subcase fully controls the value it sets.

Evidence

  • Reproduced the /unset subcase failing under SPACEDOCK_BIN=$(command -v go); passes after the fix.
  • go test ./... → 1247 passed, 0 failed — both with SPACEDOCK_BIN exported and under env -u SPACEDOCK_BIN.

Test-only change; production launcher_command.go is untouched.

…CK_BIN

The runLauncherCommand helper inherited the ambient environment via
os.Environ(), so the unset subcase leaked any SPACEDOCK_BIN set by a
spacedock claude/codex session and ran the real binary instead of the
PATH fallback stub. Strip SPACEDOCK_BIN from the base env so each
subcase fully controls the value.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@clkao clkao merged commit 4082b90 into next Jun 9, 2026
3 checks passed
clkao added a commit that referenced this pull request Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant