Closed
Description
Describe the bug
If you try to stream both standardOutput
and standardError
from the Execution
in the closure-based run method, it fails with Fatal error: The standard output has already been consumed
.
To Reproduce
Steps to reproduce the behavior:
- Attempt to access
execution.standardOutput
andexecution.standardError
in the same run closure.
Expected behavior
It should be possible to access both sequenced outputs.
Environment (please complete the following information):
- OS: macOS 15.4.1 (24E263)
- Swift version: swiftlang-6.1.0.110.21 clang-1700.0.13.3
Additional context
This looks like a simple copy/paste bug in Execution.swift
, the consumption state is checking for .standardOutputConsumed
rather than . standardErrorConsumed
for the standardError
case.