StreamSelectLoop: Int overflow for big timer intervals #95
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The problem
As described here, current
StreamSelectLoop
implementation restricts using time intervals more thanPHP_INT_MAX
microseconds. For 32-bit systems it's only 2148 seconds.Suggested solution
StreamSelectLoop
$timeout
type fromint
(in microseconds) tofloat
(in seconds);usleep
withtime_nanosleep
, causeusleep
takesint
argument in microseconds, and we can't keep more thanPHP_INT_MAX
microseconds. Buttime_nanosleep
takes 2 arguments:int
amount of seconds andint
amount of nanoseconds, that allowsStreamSelectLoop
to handlePHP_INT_MAX
seconds intervals;stream_select
andtime_nanosleep
methods calls fromStreamSelectLoop::streamSelect(...)
to test timeout values.