When raising error for using generators in spans, link to the official page

[baggiponte]

Description

Hello there! I got an instance of this error:

Failed to detach context
Traceback (most recent call last):
  File "async_generator_example.py", line 11, in generate_items
    yield i
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "opentelemetry/context/__init__.py", line 154, in detach
    _RUNTIME_CONTEXT.detach(token)
  File "opentelemetry/context/contextvars_context.py", line 50, in detach
    self._current_context.reset(token)
ValueError: <Token var=<ContextVar name='current_context' default={} at 0x10afa3f60> at 0x10de034c0> was created in a different Context

And only after a bit of search I was able to find the documentation page about it.

What if the SDK added this link as a note to the Exception so that users can immediately see the reference and see if that applies?

[alexmojaki]

The error isn't raised/logged/catchable within logfire. But I would like it if logfire.span emitted a warning (with an option to ignore it) when called within a generator function.

[dhruv-ahuja]

@alexmojaki can I take this one up?

[baggiponte]

The error isn't raised/logged/catchable within logfire.

That's because it's a "generic" ValueError right?

But I would like it if logfire.span emitted a warning (with an option to ignore it) when called within a generator function.

How would you do that?

[alexmojaki]

The error isn't raised/logged/catchable within logfire.

That's because it's a "generic" ValueError right?

No, because it's caught (and logged) by OTel and doesn't bubble up within our reach.

But I would like it if logfire.span emitted a warning (with an option to ignore it) when called within a generator function.

How would you do that?

#1430 has the right idea.