Skip to content
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.

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

Crescendo should probably set $PSNativeCommandUseErrorActionPreference = $false #186

Closed
3 tasks done
JamesWTruher opened this issue Dec 9, 2022 · 1 comment
Closed
3 tasks done
Labels
Issue-Enhancement New feature or request Issue-Triaged issue was read and triaged

Comments

@JamesWTruher
Copy link
Member

Prerequisites

  • Write a descriptive title.
  • Make sure you are able to repro it on the latest released version
  • Search the existing issues.

Steps to reproduce

because setting $PSNativeCommandUseErrorActionPreference = $true will result in an additional error record being produce in the case of an error, crescendo should probably set this variable explicitly now that we handle error output as part of push-crescendoerror. Perhaps it should be settable on a command by command basis (add it to the schema for a command???)

Expected behavior

a single error

Actual behavior

2 errors

Error details

PS> /bin/ls a
ls: a: No such file or directory
NativeCommandExitException: Program "ls" ended with non-zero exit code: 1.

Environment data

Name                           Value
----                           -----
PSVersion                      7.3.0-daily20221207.1
PSEdition                      Core
GitCommitId                    7.3.0-daily20221207.1
OS                             Darwin 22.1.0 Darwin Kernel Version 22.1.0: Sun Oct  9 20:14:54 PDT 2022; root:xnu-8792.41.9~2/RELEASE_X86_64
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Version

all

Visuals

No response

@theJasonHelmick theJasonHelmick added Issue-Enhancement New feature or request Issue-Triaged issue was read and triaged labels Dec 9, 2022
@theJasonHelmick theJasonHelmick added this to the Investigating milestone Dec 9, 2022
@theJasonHelmick
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Enhancement New feature or request Issue-Triaged issue was read and triaged
Projects
None yet
Development

No branches or pull requests

2 participants