New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ident_func when running within gunicorn+gaiohttp #730
Comments
the default is only aware of greenlets/threads, its unclear how to deal with something more complex LocalManager can be given a custom ident function in the constructor, but its unclear how to determine the deployment situation |
Maybe we can combine all available task identifiers? Something like that:
|
I don't like the performance implications of that. I suppose if e.g. |
I wonder if we could use |
Similar thing can be achieved by using |
Any chances to get that one resolved somehow? We can determine which eventloop is used just once at the startup, that won't cause any performance issues. |
Sounds like it's already customizable. Any better detection will happen as we add support for ASGI, rolling this into #1322 |
LocalManager.ident_func
should be set toasyncio.Task.current_task
when running under gunicorn+gaiohttp.Currently if we're running with gaiohttp the LocalManager mixes the context of different tasks :(
Have no idea how to properly implement the detection if we're running under eventlet (under python3) or asyncio, just hacked my own greenlet module which returns the proper task id.
The text was updated successfully, but these errors were encountered: