[Process] Fixed escaping arguments on Windows when inheritEnvironmentVariables is set to false #22614
Conversation
|
Calling |
|
OK. I actually don't use this functionality :-). I just noticed it was not working when I was debugging the failing tests and considered it a BC break. I've updated the PR to fix this. |
| $var = $uid.++$varCount; | ||
| putenv("$var=\"$value\""); | ||
|
|
||
| if ($env === null) { |
There was a problem hiding this comment.
yoda style: null === $env
| if ($env === null) { | ||
| putenv("$var=$value"); | ||
| } else { | ||
| $env[$var] = $value; |
There was a problem hiding this comment.
Because of line 1656 above, $value will be quoted. It shouldn't, isn't it?
There was a problem hiding this comment.
@nicolas-grekas
I thought the same at the beginning but the argument needs to be escaped even it's passed using the !var! notation (and stored inside the env vars). The tests don't pass without the quotes. BTW I am not exactly sure why it's done using the !var! workarround. Looks like a clever trick and perhaps you are it's author (due to github history/annotations). Is it somehow related to how inconsistently Windows commands handle unescaping of double quotes? (Should be mostly triple quotes and i've found an article describing it but it's not exactly specified so some commands handle it differently). I'm just curious :-)
|
@maryo Can you rebase here? I have fixed the base branch given that master now is for Symfony 4.0, but the PR now contains unrelated commits. |
|
please rebase on 3.3 (there should be no merge commit it the PR history) |
…tEnvironmentVariables is set to false
|
Thank you @maryo. |
…EnvironmentVariables is set to false (maryo) This PR was merged into the 3.3 branch. Discussion ---------- [Process] Fixed escaping arguments on Windows when inheritEnvironmentVariables is set to false | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | no | Fixed tickets | | License | MIT | Doc PR | I've added a FAILING testcase on Windows. It incorrectly substitutes an argument containing a quotation mark probably assuming it's an env var needed to backup when inheritEnvironmentVariables is set to false. Commits ------- 26032ef [Process] Fixed incorrectly escaping arguments on Windows when inheritEnvironmentVariables is set to false
I've added a FAILING testcase on Windows. It incorrectly substitutes an argument containing a quotation mark probably assuming it's an env var needed to backup when inheritEnvironmentVariables is set to false.