Fix email zone #8073
Merged
Fix email zone #8073
Conversation
This file contains hidden or 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
2 participants
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.
Further follow-up to Execute email sending in its own zone. #8047 in the context of Unhandled exception when SMTP sockets are closed #8032.
The first commit is only refactoring and generalizing the gmail relay email sender logic: abstracting the connection, the sending and its lifecycle handling.
The second commit fixes the in-zone unhandled exception interception by using a Completer + microtask to have a coordinated path for in-request regular result or exceptions, while also tracking out-of-request async errors and invalidating the connection when such happens. (Verified by tests).