-
Notifications
You must be signed in to change notification settings - Fork 16
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
Force expiration only if memo still exists #16
Force expiration only if memo still exists #16
Conversation
Seems legit! Do you mind adding a relevant unit test to cover this change? |
I would be happy to! I'm having trouble running the tests. Seems
|
Try |
If you're running the tests on OSX Sierra, you'll probably run into this issue as well. If you do and wouldn't mind, bump the version of |
a6f8bdc
to
3534387
Compare
This is updated with a unit test! 🎉 There is now a PhantomJS launcher |
@allantokuda-zipnosis Yes please! |
Updated. Is this good to go? |
Released in 0.1.2! |
This should prevent errors of this type:
This can happen because this code is executed in a promise error callback, which is not in the same event loop as where the memo is created on line 163. Between the time the memo was created and the time of line 217's execution, line 257
delete memos[key]
could have already executed.This helps ensure stability of applications that pass in an
expireOnFailure
function.