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
My production app works as expected when not instrumented. After adding asyncio instrumentation, various components of our app simply "didn't run". No explicit errors are thrown, but for a concrete example, messages published via a redis pubsub were not delivered since there were no subscribers. After disabling the instrumentation, subscriptions occurred.
I found a commonality between all the code that "didn't run", which was that they all involved methods that yielded.
$ python3 main.py
<async_generator_asend object at 0x7b0fa554ae80>
Additional context
Our first usage of this package was 0.45b0, which we had to disable due to #2340. It appears the emphasis was on 'don't crash'; the first fix simply did an early return. It was noticed during review, and after addressing, it was noted (#2521 (comment)) that it "somehow worked" whether the coro was returned or not.
The original reproducer (#2340 (comment)) is nearly identical to my reproducer. The only meaningful difference is that the original reproducer (nor the test case) did not actually look at the results, whereas mine (and my production app) does.
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered:
Describe your environment
OS: Ubuntu 22.04.4 LTS
Python version: Python 3.12.3
Package version: 0.47b0 (and main)
What happened?
My production app works as expected when not instrumented. After adding asyncio instrumentation, various components of our app simply "didn't run". No explicit errors are thrown, but for a concrete example, messages published via a redis pubsub were not delivered since there were no subscribers. After disabling the instrumentation, subscriptions occurred.
I found a commonality between all the code that "didn't run", which was that they all involved methods that
yield
ed.Steps to Reproduce
main.py:
Expected Result
Actual Result
Additional context
Our first usage of this package was
0.45b0
, which we had to disable due to #2340. It appears the emphasis was on 'don't crash'; the first fix simply did an early return. It was noticed during review, and after addressing, it was noted (#2521 (comment)) that it "somehow worked" whether the coro was returned or not.The original reproducer (#2340 (comment)) is nearly identical to my reproducer. The only meaningful difference is that the original reproducer (nor the test case) did not actually look at the results, whereas mine (and my production app) does.
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: