The __exit__(None, None, None) call in the finally block always passes None for the exception arguments, even when an exception occurs during the yield. The Span.__exit__ method (lines 396-406 in tracing.py) checks if value is not None to set INTERNAL_ERROR status on the span. Since value is always None, GraphQL errors will not be reflected in the span's status.

The finally block calls _graphql_span.__exit__(None, None, None) unconditionally, discarding exception information. The span's __exit__ method checks if value is not None and should_be_treated_as_error(ty, value) to set SPANSTATUS.INTERNAL_ERROR, but since None is always passed, spans won't be marked as errored even when exceptions occur during GraphQL execution. This affects observability when unexpected exceptions propagate.