You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
stream_socket_client throws fatal error if network is unreachable #328
@valzargaming Thanks for reporting, I'm still trying to understand what's going on here. The stream_socket_client() function never throws on its own, it only reports an E_WARNING on error or reports a SO_ERROR later on the socket. Both of these error classes are handled by the code following the stream_socket_client() function and the entire code has 100% code coverage including any errors cases.
Can you help us reproduce the problem you're seeing?
Specifically, please provide a gist that allows us the see the error you're seeing.
Could this perhaps be related to a custom error handling (set_error_handler() function like Improve error reporting when custom error handler is used #290)? If so, what does it look like and what makes you think this is an error in ReactPHP rather than the custom error handler?
Activity
clue commentedon Oct 25, 2025
@valzargaming Thanks for reporting, I'm still trying to understand what's going on here. The
stream_socket_client()function never throws on its own, it only reports anE_WARNINGon error or reports aSO_ERRORlater on the socket. Both of these error classes are handled by the code following thestream_socket_client()function and the entire code has 100% code coverage including any errors cases.Can you help us reproduce the problem you're seeing?
Specifically, please provide a gist that allows us the see the error you're seeing.
Could this perhaps be related to a custom error handling (
set_error_handler()function like Improve error reporting when custom error handler is used #290)? If so, what does it look like and what makes you think this is an error in ReactPHP rather than the custom error handler?Thank you.
valzargaming commentedon Oct 28, 2025
I'll take a closer look at this later this week, but I believe 3 is the likely culprit.