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.

Sign up for GitHub

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

Jump to bottom

Add installer error to the output when providing expected return codes #1890

Open
denelon opened this issue Feb 1, 2022 · 1 comment
Open

Add installer error to the output when providing expected return codes #1890

denelon opened this issue Feb 1, 2022 · 1 comment
Labels
Area-Output Issue related to CLI output Issue-Feature This is a feature request for the Windows Package Manager client.

Comments

@denelon
Copy link
Contributor

denelon commented Feb 1, 2022

Description of the new feature / enhancement

When the installer provides an error code mapped to an expected return code, the specific installer error should be included in the output. This may help when multiple return codes are mapped to a single expected return code.

"Return response code from installer: "

Proposed technical implementation details

No response
@denelon denelon added the Issue-Feature This is a feature request for the Windows Package Manager client. label Feb 1, 2022
@ghost ghost added the Needs-Triage Issue need to be triaged label Feb 1, 2022
@denelon denelon removed the Needs-Triage Issue need to be triaged label Feb 1, 2022
This was referenced Aug 20, 2022
Open
Open
@Trenly
Copy link
Contributor

Trenly commented Jun 16, 2023

[Policy] Area-Output

@microsoft-github-policy-service microsoft-github-policy-service bot added the Area-Output Issue related to CLI output label Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Output Issue related to CLI output Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Trenly @denelon