Skip to content

🧪 test(kanban): isolate HERMES_KANBAN_ORIGIN in the hermetic env fixture #125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cwest merged 1 commit into from
Aug 17, 2026
Merged

🧪 test(kanban): isolate HERMES_KANBAN_ORIGIN in the hermetic env fixture #125

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions tests/conftest.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,6 +214,14 @@ def _looks_like_credential(name: str) -> bool:
"HERMES_KANBAN_RUN_ID",
"HERMES_KANBAN_CLAIM_LOCK",
"HERMES_KANBAN_DISPATCH_IN_GATEWAY",
# The card-origin channel (gateway/session_context._KANBAN_ORIGIN_ENV).
# A dispatched worker inherits this across the spawn boundary; under bare
# pytest (no CI wrapper) it leaks into every test, so
# _maybe_auto_subscribe resolves a real origin and auto-subscribes even
# when a test has cleared the HERMES_SESSION_* vars. Scrub it alongside
# the other kanban pins so subscription tests see a truly detached
Comment thread
cwest marked this conversation as resolved.
# context.
"HERMES_KANBAN_ORIGIN",
"HERMES_TENANT",
# Honcho host selection changes which nested config block wins. A local
# shell override leaked "myhost" into the full suite and flipped 20
Expand Down
Loading