Use the Init and Exit error signals provided by the Extension API #145
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.
Motivation
This PR resolves #140. If an error occurs during registration, the
InitError
signal is sent to the Lambda runtime. If an error occurs when requesting the next event, theExitError
signal is sent to the Lambda runtime. The observed behavior upon reception of these signals is that the runtime exits cleanly and displays the received error.Files changes
All the changes are in
main.go
. Aside from the implementation of those signals, two snippets have been added for testing purposes (and will be removed before merge).Behavior
InitError
sent after the extension attempts to registerResponse
Behavior
Comparison : crash (
main.go
returns) after the extension attempts to registerResponse
Behavior
ExitError
sent after the extension receives a new eventResponse
Behavior
Comparison : crash (
main.go
returns) after the extension receives a new eventResponse
Behavior
Pending points
InitError
andExitError
signals ?