Handle Signal Exceptions during Runtime API Http Requests Gracefully and Version Bump to 3.1.3 #50
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.
Handle Signal Exceptions during Runtime API Http Requests Gracefully and Version Bump to 3.1.3
Issue #, if available: #28
Description of changes: Handle the Ruby HTTP library SignalExceptions when receiving SIGTERM/SIGKILL/Interrupt/etc... and shutdown gracefully without polluting customer logs with a false positive exception log.
Target (OCI, Managed Runtime, both): Managed Runtimes (When using Extensions).
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.