Lines from conf files that are comments should not be passed to shell.Expand #374
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #373
Currently, all lines in a file from
conf.dwill be passed toshell.Expandno matter if they are comments or not. This is not a problem per se, but asshell.Expandwill refuse to do command substitution (as to prevent execution of arbitrary code), comments containing either$(cmd)orcmdstyle commands will raise an error.As there does not seem to be a way to adjust the behavior of
shell.Expandfurther, this PR fixes the issue by skipping lines that are obviously comments.