fd-path regression test hardcodes /proc/self/fd — Linux-only, breaks the suite on macOS #37
Labels
No labels
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-triage
ready
release
scope:apply
scope:capture
scope:coolify-api
scope:fleet
scope:manifest
scope:secrets
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: heavy-duty/cast#37
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up from the review of #35.
The regression test added in #35 (
test/secrets.test.ts, "accepts a key path only this process can resolve") builds the injected path as:/procdoesn't exist on macOS, so the test fails there — and cast runs on the operator's workstation, which may be a Mac./dev/fd/${fd}resolves on both platforms (on Linux it's a symlink to/proc/self/fd), and it's also closer to what bash actually expands<(…)to.One-line fix:
While in there, consider the FIFO-shaped companion test noted in #36 — the current fixture is a regular file, so it reproduces the path only resolvable in-process shape but not the read-once pipe shape of a real process substitution.
🤖 Generated with Claude Code