-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
UV Event Loop (PECL ext-uv) #112
Conversation
c6dcbde
to
7a359c5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, would love to see more extensions find their way into this project! 👍
c20ff88
to
3722eda
Compare
a00ba1b
to
066ada7
Compare
… off upwards as suggested by @clue at reactphp#112 (comment)
…ignal listeners attached for calling `uv_run`, modeled (copied) the bit from `ExtEvLoop` and had to rename $timerEvents to $timers (also makes more sense) as suggested by @clue at reactphp#112 (comment)
…nged and what failed before the change, as suggested by @clue at reactphp#112 (comment)
…omment) The property was only used in one method and adding more bloat than solving a problem
FYI the issues I was having wheren't related to the event loop directly but due to file descriptors being passed on child processed by default, solving that down/upstream depending on your perspective: WyriHaximus/reactphp-child-process-messenger#22 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@WyriHaximus added minor remarks only, can you squash this to a reasonable number of commits before the next review?
src/ExtUvLoop.php
Outdated
if ($status !== 0) { | ||
unset($this->flags[(int) $stream]); | ||
$this->pollStream($stream); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ping @WyriHaximus, what's the status here?
@clue will squash into one commit once everyone approves it before merging it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's happening: Squash and then let's get this in! 🎉
5374439
to
d589f9f
Compare
It is time for this PR to be merged, I've squashed all commits into one, the original unrewritten history can be found here: https://github.com/WyriHaximus-labs/event-loop/tree/blacklight-history |
No description provided.