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

[BUGFIX lts] Enable _some_ recovery of errors thrown during render. #16174

Merged
merged 1 commit into from
Jan 25, 2018

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Jan 25, 2018

If env.commit() is not called after it has started, and another env.begin() starts Glimmer throws an error:

Error: a glimmer transaction was begun, but one already exists. You may have a nested transaction

This commit works around the issue by ensuring that if a transaction had been started, it is cleaned up even if an error was thrown during render.

Fixes glimmerjs/glimmer-vm#484

If `env.commit()` is not called after it has started, and another
`env.begin()` starts Glimmer throws an error:

```
Error: a glimmer transaction was begun, but one already exists. You may have a nested transaction
```

This commit works around the issue by ensuring that if a transaction had
been started, it is cleaned up even if an error was thrown during render.
@rwjblue rwjblue merged commit e3a5652 into emberjs:master Jan 25, 2018
@rwjblue rwjblue deleted the fix-scenarios-for-transaction-error branch January 25, 2018 16:17
@GavinJoyce
Copy link
Member

I've confirmed that this restores the previous behaviour in earlier versions of Ember (for the cases in our app where we're causing exceptions)

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.

2 participants