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
Can you reproduce the bug with PYTHONASYNCIODEBUG in env?:
Does uvloop behave differently from vanilla asyncio? How?: When creating a default thread pool uvloop does not set thread name prefix
It would be great to set thread name prefix for a default thread pool used by uvloop. For example the default asyncio loop sets it to asyncio, so for uvloop it could be set to uvloop. It's useful for debugging and for example in DataDog flame graph it makes it easier to identify uvloop threads in this case. Right now it looks like this:
As I understand it should be pretty straightforward change and I could make a PR if there are no objections.
The text was updated successfully, but these errors were encountered:
PYTHONASYNCIODEBUG
in env?:uvloop
does not set thread name prefixIt would be great to set thread name prefix for a default thread pool used by
uvloop
. For example the defaultasyncio
loop sets it toasyncio
, so foruvloop
it could be set touvloop
. It's useful for debugging and for example in DataDog flame graph it makes it easier to identifyuvloop
threads in this case. Right now it looks like this:As I understand it should be pretty straightforward change and I could make a PR if there are no objections.
The text was updated successfully, but these errors were encountered: