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

Assertion Failed: expected container not to be destroyed #5570

Closed
herzzanu opened this issue Aug 16, 2018 · 4 comments
Closed

Assertion Failed: expected container not to be destroyed #5570

herzzanu opened this issue Aug 16, 2018 · 4 comments

Comments

@herzzanu
Copy link

After upgrading to 3.3 from 3.2 I get the following error in most of the tests

image

Probably related to #5465

@runspired
Copy link
Contributor

@herzzanu by 3.3 from 3.2 I assume you mean ember-source (aka ember.js). What version of ember-data are you paired with? (3.3 and 3.2 for ember-data are identical).

@runspired
Copy link
Contributor

Closing in favor of #5578. While ultimately this is an issue with ember.js upstream, the commit we can backport would make this less painful and we should backport it.

@herzzanu
Copy link
Author

@runspired ember-data is 3.2 as well, understanding it's the same as 3.3

@ballPointPenguin
Copy link

FYI I just hit this (or something similar) with

  • ember-cli 3.4.4
  • ember-data 3.4.4
  • ember-source 3.4.8

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

No branches or pull requests

3 participants