Handle in-progress events without deadlocking #63
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.
When in-progress messages are sent to the eventStream channel,
lifecycle-manager deadlocks, since there are no eventStream receivers
running in a separate goroutine. Instead of sending the in-progress
messages to the eventStream channel, we can process them immediately as
we process SQS-driven events, avoiding the deadlock.
Resolves #62