PDE-3038 fix(core): dangling logger causes Lambda to hang #490
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
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.
Fixes https://github.com/zapier/zapier/issues/53430.
The bug was introduced by #483. Affected core versions are 11.3.0 and 9.7.0. The root cause is the
httpPatch()function was reusing theloggerinstance from the previous Lambda invocation. But since we destroy the logger at the end of a Lambda call, the logger wouldn't be valid for the subsequent call. This causes the subsequent call to wait for the invalid logger to respond and time out.The symptoms of this bug: