-
Notifications
You must be signed in to change notification settings - Fork 61
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
Propagate user-level exceptions during client reset #1581
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like we still miss to update the changelog with the new Core version being used and CI needs to be green, but otherwise
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not following the updates to how the global refs on the error_user_code
are managed. Might be that I have missed something, but will have to check it out to get the insights. Or do you have any magic one liner that can give the overview?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not follow the updates to how the global refs on the
error_user_code
are managed. Might be that I have missed something, but will have to check it out to get the insights. Or do you have any magic one liner that can give the overview?
I see the connection now. I was just confused as I though it had something to do with the removed PopLocalFrame
s. But after settling that these were removed by mistake I get it.
But still think there is an erroneous asStableRef
on Darwin.
User-level exceptions were not propagated to the users via the exception channels. The exception message was printed on the stderr channel and swallowed.
This PR fixes this issue allowing the user-level exceptions to propagate all the way through the proper channels. Now it would be available as the
ClientResetFailed
throwable cause.Depends on realm/realm-core#7148
Closes #1580