-
Notifications
You must be signed in to change notification settings - Fork 41
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
flock(): Illegal operation argument #27
Comments
Hello, I assume you get this by calling |
Hello, I never called flock from my own code (or the Laravel framework does it for me) but I fixed it by always setting the LOCK_EX constant |
I use this lib on WordPress instalations. After update to 1.4 the language system is broken. Any help on it? |
* master: Fix logo image Travis: skip phpcs in case of integration tests stream_lock operation can use strict type checking when it's 0 PHP 7.1: Fixed issue with php-cs-fixer Fix bug with StreamProcessor::stream_lock explained here antecedent/patchwork#27 Test php 7.1 test for setting post method when CURLOPT_POSTFIELDS set Adds github pull request template Set POST method when CURLOPT_POSTFIELDS is set Fix parallel cURL requests: - Make sure all handles are inside an array so they can be removed properly when done - Remove handle as soon as done - Fix behaviour of curl_multi_exec to return last curl info - Also fix test, check for the second to last curl info and make sure the third returns false, not the second - CS fixes php-cs-fixer introduced (php-vcr#173)
I have found a similar issue with flock on line 192 - the issue manifested because - somehow - this module conflicts with the php codesniffer module. The main issue seems to be that the I'll check this out when I get to the office tomorrow - but I think the internals of this function could pass in operation as an integer, and that would allow consumers to call it using more appropriate methods - for example |
ErrorException in Stream.php line 176: flock(): Illegal operation argument
I can fix this error by setting LOCK_EX
The text was updated successfully, but these errors were encountered: