Powershell script returns an exit code of `1` even though its executing successfully
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 133
- Forks
- 73
- Avg merge
- 8h 20m
- Merged PRs (30d)
- 2
Description
Version: 2.3.2-universal-mingw32
[Version of the project installed]
Environment: Windows 11
[Details about the environment such as the Operating System, cookbook details, etc...]
Scenario: When running powershell scripts , the script is exiting with a status code of 1 rather then 0 even though the script is working fine
[What you are trying to achieve and you can't?]
Steps to Reproduce:
[If you are filing an issue what are the things we need to do in order to repro your problem?]
Expected Result:
[What are you expecting to happen as the consequence of above reproduction steps?]
Actual Result:
[What actually happens after the reproduction steps?]
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
The issue names no source files, tests, or reproducible commands. Start by obtaining the missing PowerShell command and expected and actual exit behavior on Windows 11 with version 2.3.2-universal-mingw32; done means reproducing the nonzero status and adding a regression test for the corrected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, ruby
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100