Skip to content
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

Fix issue with unchaining ChainNodes (again) #15982

Merged
merged 2 commits into from
Dec 14, 2017
Merged

Fix issue with unchaining ChainNodes (again) #15982

merged 2 commits into from
Dec 14, 2017

Conversation

chancancode
Copy link
Member

@chancancode chancancode commented Dec 14, 2017

cc @bekzod

This reverts commit 1396bec.

From @krisselden

> This is a serious bug and this doesn't actually fix the issue,
> some refactoring to ember-metal has caused overriding watch to
> issue unbalanced watch/unwatch calls. It needs to be bisected.
When mutating the chains (`remove()` here) we must call `writableChains()`
to "fork" it from the parent.
@krisselden
Copy link
Contributor

Why did the revert commit pass if you kept the test?

@chancancode
Copy link
Member Author

#15983 on its own is failing as expected. I think I just confused travis here.

@chancancode chancancode deleted the fix-chains branch December 14, 2017 17:08
if (paths[path] > 0) {
paths[path]--;
} else {
return;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not to add assert here to know that there was unbalanced unchain or is it too much ? @krisselden

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants