-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
symfony/process throws error when trying to unlink temp file on windows since 3.0.8 #19416
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
Comments
This error shoudn't happen: the call to unlink is prefixed by the silencing operator. It looks like your error handler is broken... |
Anyway, could you please try #19427? |
Tried and now at least the error isn't a fatal one, it actually proceeds the execution of the code. I am running this with xdebug enabled, with it disabled after this PR the errors disappears, before this PR even with xdebug disabled the fatal error is thrown, even after i tried a fresh php.exe 7.0.9 With xdebug enabled now it throws the following stacktrace
At least now it isn't a fatal error anymore just a warning so no problems. |
You must have xdebug.scream enabled in your php.ini, isn't it? Then you should disable it, this is only a debugging option that can't be compatible with normal runtime behavior of any php apps. |
…olas-grekas) This PR was merged into the 2.7 branch. Discussion ---------- [Process] Fix write access check for pipes on Windows | Q | A | ------------- | --- | Branch? | 2.7 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #19336, #19416 | License | MIT | Doc PR | - Commits ------- 66e694e [Process] Fix write access check for pipes on Windows
This occurs when i try to composer update a laravel project:
Downgrading to 3.0.7 fix this issue.
Results from debugging:
This issue is caused since this change #19118 and may be related to issue #19336
Thrown in the line 62 of src/Symfony/Component/Process/Pipes/WindowsPipes.php
The PHP function
is_writtable
returnstrue
to both$file
and$tmpDir
.Removing the
@
from the calls gives no extra infos.Also
var_dump(error_get_last())
; returnsnull
.The file exists and it is deleted after the error (the error kill the proccess though) so it may be an issue with another process using the file at the same time?
Using Windows 10 x64 php 7.0.6 composer .
Previously added this as a comment on that issue but it seems a different issue.
Didn't break anything on the projects that i've tested so far so it probably doesn't have a big impact apart from the scary message.
If there's any info's that are required i can provide it.
The text was updated successfully, but these errors were encountered: