-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
remove test waiter #5544
remove test waiter #5544
Conversation
if (DEBUG) { | ||
this.__asyncRequestCount = 0; | ||
|
||
Ember.Test.registerWaiter(() => { |
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.
This requires a sibling Ember.Test.unregisterWaiter(fn)
or it will leak
return ASYNC_REQUEST_COUNT === 0; | ||
}); | ||
} | ||
|
||
export function guardDestroyedStore(promise, store, label) { | ||
let wrapperPromise = resolve(promise, label).then(v => promise); | ||
|
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.
can we put the incrementer here? If so, that would likely bit-rot related tester waiter imbalances.
* remove test waiter * Add store encapsulated waiter * dont leak waiters * if debug add bugs * make calls symetrical (cherry picked from commit a5f1d41)
* remove test waiter * Add store encapsulated waiter * dont leak waiters * if debug add bugs * make calls symetrical
The test waiter is prone to pwn-ing folks with the current implementation. New implementation to follow.