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

Making sure remotely thrown (non-hpx) exceptions are properly marshaled back to invocation site #4887

Merged
merged 1 commit into from Aug 8, 2020

Conversation

hkaiser
Copy link
Member

@hkaiser hkaiser commented Aug 7, 2020

Fixes #4886

@NK-Nikunj this should solve the issue you reported

@aurianer I think this should be part of the upcoming release as it fixes a serious problem with remote exception handling

Copy link
Member

@NK-Nikunj NK-Nikunj left a comment

Choose a reason for hiding this comment

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

I confirm that it works now. Thanks a lot!

@hkaiser hkaiser merged commit 60ad7e9 into master Aug 8, 2020
@hkaiser hkaiser deleted the fixing_4886 branch August 8, 2020 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A future bound to an action executing on a different locality doesn't capture exception state
2 participants