Skip to content

Conversation

@rosen-vladimirov
Copy link
Contributor

Different node versions have different behaviors of timers. In some cases, on some machines we throw error that future is resolved more than once.
Prevent it.

@rosen-vladimirov rosen-vladimirov self-assigned this Nov 20, 2015
@rosen-vladimirov rosen-vladimirov added this to the 1.5.0 milestone Nov 20, 2015
@ns-bot
Copy link

ns-bot commented Nov 20, 2015

Test PASSed.

@teobugslayer
Copy link
Contributor

👍

1 similar comment
@vchimev
Copy link

vchimev commented Nov 20, 2015

👍

Different node versions have different behaviors of timers. In some cases, on some machines we throw error that future is resolved more than once.
Prevent it.
@rosen-vladimirov rosen-vladimirov force-pushed the vladimirov/fix-future-resolved-more-than-once branch from f44b1c7 to 66d0537 Compare November 20, 2015 13:57
@ns-bot
Copy link

ns-bot commented Nov 20, 2015

Test PASSed.

rosen-vladimirov added a commit that referenced this pull request Nov 20, 2015
…lved-more-than-once

Prevent Future resolved more than once errors
@rosen-vladimirov rosen-vladimirov merged commit 2c8ce46 into release Nov 20, 2015
@rosen-vladimirov rosen-vladimirov deleted the vladimirov/fix-future-resolved-more-than-once branch November 20, 2015 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants