fix(wsgi): Ensure span stays active throughout the response iteration #821
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.



Long story short
Our existing WSGI middleware implementation did not consider the fact that WSGI applications return an iterable object.
The long story
Examples:
• Returning a list: This is a common approach for smaller, complete responses.
• Using a generator: This allows for streaming and lazy generation.
Important Considerations:
• close() Method: If the returned iterable has a close() method, the WSGI server is responsible for calling it upon completion of the request, allowing the application to release any resources. [1]