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
In ReactNativeTimersIdlingResource, "idle" timer can shadow the existence of a "busy" timer waiting in queue, causing isIdle() to falsely return true.
To be specific, this iteration tries to find the next timer, rather than the next busy timer. Thus, in the case where the next timer to pop happens to be a long one (duration > 1500ms), isIdle() would always return true -- even there's another timer waiting with a short duration whose target time happens to be past the 1st one's.
Steps to Reproduce
Pretty rare.
Detox, Node, Device, Xcode and macOS Versions
N/A
The text was updated successfully, but these errors were encountered:
Description
In
ReactNativeTimersIdlingResource
, "idle" timer can shadow the existence of a "busy" timer waiting in queue, causingisIdle()
to falsely returntrue
.To be specific, this iteration tries to find the next timer, rather than the next busy timer. Thus, in the case where the next timer to pop happens to be a long one (duration > 1500ms),
isIdle()
would always returntrue
-- even there's another timer waiting with a short duration whose target time happens to be past the 1st one's.Steps to Reproduce
Pretty rare.
Detox, Node, Device, Xcode and macOS Versions
N/A
The text was updated successfully, but these errors were encountered: