Skip to content

Conversation

saghul
Copy link
Member

@saghul saghul commented Jan 27, 2015

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That comment is a bit superfluous, isn't it? :-)

@bnoordhuis
Copy link
Member

LGTM. Maybe the commit log can go into a little more detail.

Switch from running the loop with UV_RUN_ONCE to UV_RUN_DEFAULT, because
it's possible that the poll returns earlier than expected and thus the
timer is not run on a single interation.

The loop is not stopped either from the timer callback or from the async
handle's.
@saghul
Copy link
Member Author

saghul commented Jan 27, 2015

Fixed, can you PTAL?

@bnoordhuis
Copy link
Member

LGTM. @rvagg?

@rvagg
Copy link
Member

rvagg commented Jan 27, 2015

yes, this is excellent, thanks @saghul

additional context to explain what's going on here for the record libuv/libuv#168

rvagg pushed a commit that referenced this pull request Jan 27, 2015
Switch from running the loop with UV_RUN_ONCE to UV_RUN_DEFAULT, because
it's possible that the poll returns earlier than expected and thus the
timer is not run on a single interation.

The loop is not stopped either from the timer callback or from the async
handle's.

PR-URL: #622
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Rod Vagg <[email protected]>
@rvagg
Copy link
Member

rvagg commented Jan 27, 2015

landed @ b50fea4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants