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
It happens rarely, so this may not be tremendously high priority - but I'm reporting so if someone else hits this, they may add to the body of evidence pointing to the underlying issue.
Environment
Python 3.11.6 on macOS Sonoma v14.1.1
Steps to reproduce
1. Run a simple Flask web server with otel instrumentation:
Unfortunately, it is not always reproducible. Sometimes the app must be running for >5 minutes. Sometimes it happens immediately.
Expected behavior
Console exporter prints metrics to stdout
OTLP exporter errors out print to stdout
What is the actual behavior?
When the deadlock occurs, the traceback looks like this:
...
File "/opt/homebrew/Cellar/python@3.11/3.11.6_1/Frameworks/Python.framework/Versions/3.11/lib/python3.11/threading.py", line 1123, in join
self._wait_for_tstate_lock(timeout=max(timeout, 0))
File "/opt/homebrew/Cellar/python@3.11/3.11.6_1/Frameworks/Python.framework/Versions/3.11/lib/python3.11/threading.py", line 1139, in _wait_for_tstate_lock
if lock.acquire(block, timeout):
The text was updated successfully, but these errors were encountered:
If this happens again, please include the complete traceback, do not leave out any part since that information can actually show us the where in our code is the failure coming from.
Summary
Setting up multiple metrics readers like this:
causes a deadlock.
Caveat
It happens rarely, so this may not be tremendously high priority - but I'm reporting so if someone else hits this, they may add to the body of evidence pointing to the underlying issue.
Environment
Python 3.11.6 on macOS Sonoma v14.1.1
Steps to reproduce
1. Run a simple Flask web server with otel instrumentation:
2. Send requests to the endpoint
3. Wait for the deadlock
Unfortunately, it is not always reproducible. Sometimes the app must be running for >5 minutes. Sometimes it happens immediately.
Expected behavior
What is the actual behavior?
When the deadlock occurs, the traceback looks like this:
The text was updated successfully, but these errors were encountered: