fix: app-service-configurable issue 74 #383
Merged
Conversation
This file contains 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
Signed-off-by: charles-knox-intel <44684517+charles-knox-intel@users.noreply.github.com>
lenny-goodell
approved these changes
Jun 17, 2020
|
recheck |
|
closes #384 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Signed-off-by: charles-knox-intel 44684517+charles-knox-intel@users.noreply.github.com
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The
ctrl+Cinterrupt signal from the keyboard is not being correctly handled in downstream app services.Issue Number: edgexfoundry/app-service-configurable#74
What is the new behavior?
The proper
contextis now being passed to clients during app services bootstrap, which in turn allows the interrupt signal event to be handled by downstream client handlers.Does this PR introduce a breaking change?
Are there any new imports or modules? If so, what are they used for and why?
No
Are there any specific instructions or things that should be known prior to reviewing?
Downstream repositories will need to be updated in order to receive this bugfix.
Other information
N/A