8000 The error "stream_select(): No stream arrays were passed" is being generated by ProcessPipes.php · Issue #9280 · symfony/symfony · GitHub
[go: up one dir, main page]
Skip to content

The error "stream_select(): No stream arrays were passed" is being generated by ProcessPipes.php #9280

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.

Sign up for GitHub

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

Jump to bottom
Closed
jfposton opened this issue Oct 11, 2013 · 1 comment
Closed

The error "stream_select(): No stream arrays were passed" is being generated by ProcessPipes.php #9280

jfposton opened this issue Oct 11, 2013 · 1 comment

Comments

@jfposton
Copy link
Contributor

Recent changes in either 2.3.5 or 2.3.6 have caused stream_select() to throw this error:

[type] => 2
[message] => stream_select(): No stream arrays were passed
[file] => .../symfony/symfony/src/Symfony/Component/Process/ProcessPipes.php
[line] => 261

Even though the error is suppressed the error can still be retrieved with error_get_last(). This is causing issues for my custom shutdown function because the error is still present at the end of the script's execution.
jfposton added a commit to jfposton/symfony that referenced this issue Oct 24, 2013
@jfposton
Check if the pipe array is empty before calling stream_select()
e636a40 
The pipe array is either set to null or is empty occasionally when readStreams() is called. This generates a warning frequently which can cause issues for custom shutdown functions. Adding a check to see if the pipe array is empty should be functionally equivalent without having to generate the error.

Fixes: symfony#9280
This was referenced Oct 24, 2013
Closed
Closed
@isimmons
Copy link
isimmons commented Nov 8, 2013

Getting this error on composer update when

"post-update-cmd": [
    "php artisan clear-compiled",
    "php artisan optimize"
],

is present. Plus a possibly related issue with clear-compiled because bootstrap/compiled.php does not exist.

If I remove these commands the update goes through but then putting the commands back causes the same errors on the next composer update.

How to get around this?

Update Re the issue below. Now it is only the optimize command throwing the error from symfony and it only happens on a linux vagrant box with php5.5. On the windows host machine with php5.4 this is not a issue

fabpot added a commit that referenced this issue Nov 15, 2013
@fabpot
bug #9367 [Process] Check if the pipe array is empty before calling s…
2375046 
…tream_select() (jfposton)

This PR was submitted for the master branch but it was merged into the 2.2 branch instead (closes #9367).

Discussion
----------

[Process] Check if the pipe array is empty before calling stream_select()

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #9280
| License       | MIT
| Doc PR        |

ProcessPipes generates a warning frequently which can cause issues for custom shutdown functions. Adding a check to see if the pipe array is empty should be functionally equivalent without having to generate the error.

Fixes: #9280

Commits
-------

12f95e2 [Process] Check if the pipe array is empty before calling stream_select()
@fabpot fabpot closed this as completed Nov 15, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@fabpot @isimmons @jfposton
0