Correctly identify the source of the event when notifying of abnormal termination by a proces #3301
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
April 6, 2017 20:50
… termination by a process Signed-off-by: Ralph Castain <[email protected]>
…ng the VM. Signed-off-by: Ralph Castain <[email protected]>
Contributor
Author
|
@abouteiller My apologies - turned out I had this branch sitting on my machine for the last month. This fixes the problem we discussed regarding providing the correct source in event notification of abnormal termination. |
27 tasks
ggouaillardet
referenced
this pull request
May 8, 2017
Signed-off-by: Gilles Gouaillardet <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also, Fix a potential segfault by avoiding NULL topologies prior to launching the VM.