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
We got a bug report our way in sinonjs/fake-timers#66, which basically boils down to that tape ends up using stubbed timing functions and gets stuck. Mocha solves this issue by saving references to all global timing related functions, such as setTimeout, setInterval, nextTick, ..., so that later modifications will not interfere with its internal use of them.
Yeah, seems like a reasonable way of resolving this - though one might also argue that clocks should never be messed with. But it probably has its uses, so hey
- [New] make object-inspect depth configurable for expected/actual (#293)
- [New] add message defaults to .ok() and .notOk() (#261)
- [Robustness] be robust against the global `setTimeout` changing (#292)
- [Deps] update `glob`, `object-inspect`
- [Dev Deps] update `js-yaml`
We got a bug report our way in sinonjs/fake-timers#66, which basically boils down to that
tape
ends up using stubbed timing functions and gets stuck. Mocha solves this issue by saving references to all global timing related functions, such assetTimeout
,setInterval
,nextTick
, ..., so that later modifications will not interfere with its internal use of them.This would be the easiest fix.
Relevant lines that uses
nextTick
:The text was updated successfully, but these errors were encountered: