-
-
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
[BUGFIX] Fix flushing of pending saves, that include a deleted record #4994
Conversation
No idea why AppVeyor has failed, I cannot see any errors in their log... |
d445461
to
f1f9723
Compare
Unfortunately the latest releases do not include this. As the problem is quite obvious and the fix uncontroversial, I hope this can be merged sooner than later, so pinging a few folks here... @bmac @stefanpenner @igorT @runspired @pangratz |
👌 |
Sorry about that @simonihmig. I've been busy and missed this pr. Ember Data 2.14.1 has been published with this fix. |
@bmac no problem, thanks for the quick follow up release! 👍 |
this broke the build |
|
fixed with -> #5030 i think |
Sorry about that @stefanpenner. We should look into setting up @homu on this repo again, because the pr looked green when I merged it. |
@bmac ya github is misleading |
@bmac @stefanpenner Sorry about that! 😩 Still not sure why tests were passing locally and on Travis when PR was created? Or did something on master change meanwhile that caused this? |
Ember Data 2.12 introduced a bug which prevents destroys and saves happening within the same run loop. We had originally updated Ember to 2.13 and then found this issue when testing repeaters which routinely destroy and save within the same run loop, thus exposing the problem. Since this bug is subtle and may be present in unknown places elsewhere in the codebase, it was determined that downgrading to 2.11.* makes the most sense as a temporary fix until the project can eventually be updated to the latest version of Ember Data. We originally attempted upgrading to several NEWER version of Ember Data (instead of downgrading), but there were many other test failures that showed up and not enough time to fix the root causes, so this is a sensible temporary fix. bug introduced = emberjs/data#4668 bug reported = emberjs/data#4993 bug fixed = emberjs/data#4994
Fixes #4993
Seems the regression was introduced with #4668, by refactoring from a
forEach
loop to afor
loop, where we cannot simplyreturn
anymore: 063b3e5#diff-fd4c34d9a34dfde73cd3413128a3c973R1866