-
Notifications
You must be signed in to change notification settings - Fork 255
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
Chocolatey GUI doesn't write to chocolatey.log #697
Labels
5 - Released
The issue has been resolved, and released to the public for consumption
Improvement
Issues that enhances existing functionality, or adds new features
Milestone
Comments
ferventcoder
added
:Chocolatey
Blocked - External
The issue or pull request is not fixable without a change in a upstream/external library
Improvement
Issues that enhances existing functionality, or adds new features
labels
Sep 25, 2020
AdmiringWorm
added a commit
to AdmiringWorm/ChocolateyGUI
that referenced
this issue
Jun 21, 2021
This commit makes changes to how the Chocolatey API is being called, which then allows the original logging that Chocolatey implements to still happen when we add our own Serilog logger. This change depends on a new change in the Chocolatey codebase, and a new release of the program.
AdmiringWorm
added a commit
to AdmiringWorm/ChocolateyGUI
that referenced
this issue
Jun 23, 2021
This commit makes changes to how the Chocolatey API is being called, which then allows the original logging that Chocolatey implements to still happen when we add our own Serilog logger. This change depends on a new change in the Chocolatey codebase, and a new release of the program.
AdmiringWorm
added a commit
to AdmiringWorm/ChocolateyGUI
that referenced
this issue
Jan 21, 2022
This commit makes changes to how the Chocolatey API is being called, which then allows the original logging that Chocolatey implements to still happen when we add our own Serilog logger. This change depends on a new change in the Chocolatey codebase, and a new release of the program.
AdmiringWorm
added a commit
to AdmiringWorm/ChocolateyGUI
that referenced
this issue
Jan 27, 2022
This commit makes changes to how the Chocolatey API is being called, which then allows the original logging that Chocolatey implements to still happen when we add our own Serilog logger. This change depends on a new change in the Chocolatey codebase, and a new release of the program.
AdmiringWorm
added
the
3 - Review
Code has been added, and is available for review as a pull request
label
Jan 27, 2022
AdmiringWorm
added
4 - Done
Code has been added to the repository, and has been reviewed by a team member
and removed
3 - Review
Code has been added, and is available for review as a pull request
labels
Jan 27, 2022
gep13
removed
:Chocolatey
Blocked - External
The issue or pull request is not fixable without a change in a upstream/external library
labels
Feb 9, 2022
🎉 This issue has been resolved in version 0.20.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
corbob
added
5 - Released
The issue has been resolved, and released to the public for consumption
and removed
4 - Done
Code has been added to the repository, and has been reviewed by a team member
labels
Sep 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
5 - Released
The issue has been resolved, and released to the public for consumption
Improvement
Issues that enhances existing functionality, or adds new features
Chocolatey CLI writes to
C:\ProgramData\chocolatey\logs\chocolatey.log
, but Chocolatey GUI does not.This is especially confusing because the CLI output that the GUI shows says to look in the chocolatey log:
@gep13 says it's a known issue:
Possibly related to #695.
The text was updated successfully, but these errors were encountered: