The manual __enter__() and __exit__(None, None, None) calls lack exception safety. If an exception is thrown into the generator at the yield point, the code after yield (including __exit__) won't execute, leaving the span unclosed and the scope in an inconsistent state (scope.span still points to this span). Additionally, always passing (None, None, None) to __exit__ means any exception that does reach that code won't be recorded on the span's status.

The new code calls self.graphql_span.__exit__(None, None, None) unconditionally, which tells the span that no exception occurred. In the Span.__exit__ method (tracing.py:399-400), exceptions are detected via the value parameter and result in setting the span status to INTERNAL_ERROR. By always passing None, exceptions raised during GraphQL operations will not be reflected in the span's status, losing important error context for observability.