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
BUGFIX: Properly escape sub process variables on windows #182
Conversation
Windows SET command does not parse out quotes of the variable value but rather treats them as part of the value, which currently results in an error on windows since the fix for FLOW-381: Flow could not create the directory ""C:/workspace/Flow/Data/Temporary"/Development/". Note the extra quotes around the temporary base path. This change fixes that by properly escaping the SET command arguments on windows by using escapeshellcmd instead of escapeshellarg.
👍 by reading and testing on local windows 8/php5.5 |
BUGFIX: Properly escape sub process variables on windows Windows SET command does not parse out quotes of the variable value but rather treats them as part of the value, which currently results in an error on windows since the fix for FLOW-381: Flow could not create the directory ""C:/workspace/Flow/Data/Temporary"/Development/". Note the extra quotes around the temporary base path. This change fixes that by properly escaping the SET command arguments on windows by using escapeshellcmd instead of escapeshellarg. FLOW-381 #comment Regression fix for compilation on Windows
Thanks a lot for this!! |
https://jira.neos.io/browse/FLOW-425 was just reported, this change fixes that right? |
Exactly. We should create tickets for all bugs, even if we get it fixed directly. Jira should be the first point to figure out if a bug is already known to prevent multiple efforts. ----- Reply message ----- — |
i spend quite a lot of time debugging this since the error output form subrequests are not very clear (and i figured out that flow calls many times itself, maybe thats the reason why its so slow on windows...) Is it possible to do such tests with travis or does travis only support linux? |
No Windows Support in Travis. |
Ah, my fault, should have checked jira before creating the PR so quickly. Thx @kdambekalns for adding the missing jira link |
Windows SET command does not parse out quotes of the variable value but rather treats them as part of the value, which currently results in an error on windows since the fix for FLOW-381:
Note the extra quotes around the temporary base path.
This change fixes that by properly escaping the SET command arguments on windows by using escapeshellcmd instead of escapeshellarg.
FLOW-425 #close
FLOW-381 #comment Regression fix for compilation on Windows