Piping sometimes does not work on Linux
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
This was seen only on CI machines. Test failure in export test case that is doing dsc config export | dsc config set.
On local VMs this does not repro.
Error: IO: Broken pipe (os error 32)
Error: [-] resource export tests.Configuration Export can be piped to configuration Set 5.09s (5.09s|3ms)
Message
Expected 0, but got 2.
at $LASTEXITCODE | Should -Be 0, /home/runner/work/DSC/DSC/dsc/tests/dsc_export.tests.ps1:49
at <ScriptBlock>, /home/runner/work/DSC/DSC/dsc/tests/dsc_export.tests.ps1:49
Expected behavior
`dsc config export | dsc config set` always runs fine.
Actual behavior
Error above.
Error details
No response
Environment data
Linux CI VM.
Version
v1
Visuals
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the export-to-set pipeline test in tests/dsc_export.tests.ps1 at line 49 and reproduce dsc config export | dsc config set on a Linux CI environment. Trace the broken-pipe behavior in the Rust CLI and confirm that the test exits successfully and the pipeline consistently works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, rust
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100