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

Escape log output for variables that have data from external sources #565

Closed
ferventcoder opened this issue Jan 21, 2016 · 0 comments
Closed
Assignees
Milestone

Comments

@ferventcoder
Copy link
Member

If the output coming from Powershell running has {}, it throws errors because log4net sees that as a formatting variable.

@ferventcoder ferventcoder self-assigned this Jan 21, 2016
@ferventcoder ferventcoder added this to the 0.9.10 milestone Jan 21, 2016
@ferventcoder ferventcoder changed the title Escape output from Powershell log Escape log output for variables that have data from external sources Jan 21, 2016
ferventcoder added a commit that referenced this issue Jan 21, 2016
When logging messages that have variables coming from sources not under
complete control of Chocolatey, choco should escape curly braces in the
output so that the messages are logged without issues.
ferventcoder added a commit that referenced this issue Jan 21, 2016
* stable:
  (GH-563) Warn/Log Environment Variable Changes
  (GH-565) Escape output when logging external
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants