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

Determine the correct behaviour when a user requests limited output and debug #3555

Open
2 tasks done
corbob opened this issue Nov 8, 2024 · 0 comments
Open
2 tasks done

Comments

@corbob
Copy link
Member

corbob commented Nov 8, 2024

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

No response

Describe The Solution. Why is it needed?

Currently if a user requests limited output, in some places we emit the log to Debug instead of Info, and in others we don't emit anything. We should make a determination of which behaviour we want and then be consistent about it.

Additional Context

No response

Related Issues

No response

corbob added a commit to corbob/choco that referenced this issue Nov 8, 2024
The debug log is used in a lot of places when we don't want the user to
see the output, but we want it available. At the moment it is not
consistent about what we do when they select debug and limit output. It
has been decided at the moment to remove these tests as they are now
breaking by us emitting the user agent to the debug log. A follow up
issue chocolatey#3555 has been created to determine what we want for behaviour
when limit output and debug is selected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant