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

Propagate errors found during integration to kill the vessel #2064

Merged
merged 5 commits into from
Jan 14, 2019

Conversation

pleroy
Copy link
Member

@pleroy pleroy commented Jan 13, 2019

This may help with #2056 but I don't have an easy way to test. There will be a message in the WARNING log to see if we are properly handling the condition.

<< " collided with a celestial";
LOG(WARNING) << "Vessel " << vessel->ShortDebugString()
<< " collided with a celestial: "
<< future.get().ToString();
Copy link
Member

Choose a reason for hiding this comment

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

We cannot call future.get() twice, see https://en.cppreference.com/w/cpp/thread/future/get:

The behavior is undefined if valid() is false before the call to this function.
Any shared state is released. valid() is false after a call to this method.

@eggrobin eggrobin added the LGTM label Jan 13, 2019
@pleroy
Copy link
Member Author

pleroy commented Jan 13, 2019

retest this please

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

Successfully merging this pull request may close these issues.

2 participants