incrementalDelivery: fix iterable streaming with errors #3729
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 iterables (not asyncIterables) are streamed, and completeValue throws an error, we currently send undefined rather than null, due to a typo.
This change corrects the typo, and also modifies the test intended to check this case to correctly check a streamed iterable, rather than an asyncIterable.
Code coverage was complete prior to this change, because the line involving this change was reached in the case where the error was non-recoverable, albeit with the line throwing.