You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the new workflows API, there's an exception thrown:
Traceback (most recent call last):
File "/app/.venv/lib/python3.11/site-packages/opentelemetry/context/init.py", line 152, in detach
_RUNTIME_CONTEXT.detach(token)
File "/app/.venv/lib/python3.11/site-packages/opentelemetry/context/contextvars_context.py", line 50, in detach
self._current_context.reset(token) # type: ignore
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: <Token var=<ContextVar name='current_context' default={} at 0x7bd2c6f07470> at 0x7bd1b27cbf40> was created in a different Context
👟 Reproduction steps
👍 Expected behavior
👎 Actual Behavior with Screenshots
🤖 Python Version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
I checked and didn't find similar issue
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered:
I am not sure if this will help, but I was able to generate data using this:
from openinference.instrumentation.llama_index import LlamaIndexInstrumentor
from arize.otel import register
# Setup OTel via our convenience function
tracer_provider = register(
space_id = "your-space-id", # in app space settings page
api_key = "your-api-key", # in app space settings page
project_name = "your-project-name", # name this to whatever you would like
)
# Finish automatic instrumentation
LlamaIndexInstrumentor().instrument(tracer_provider=tracer_provider)
Which component is this bug for?
Llamaindex Instrumentation
📜 Description
When using the new workflows API, there's an exception thrown:
👟 Reproduction steps
👍 Expected behavior
👎 Actual Behavior with Screenshots
🤖 Python Version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: