#Integration creating many ClientSessions
1 messages · Page 1 of 1 (latest)
There really isn't a simple way to find it. We don't have tools to track down ClientSession churn becauses it not that common
I'm going to do another aiohttp release to downgrade that message to DEBUG. But the issue will still be there
I'm seeing those logs messages as well. Happy to help you testing
Just to understand. I have a few custom components. Some are using aiohttp and other httpx clients. Can I discard httpx ones?
Was it like one of those scenarios where it was always there we just never seen it before?
By the way I only added one new integration this beta and that was the Amazon devices one
Which also has that open issue with the event Loop blocking for SSL
Don't know if those are related
Its some integration that is churning aiohttp ClientSessions so no need to look at httpx
But for amazon devices it used httpx and blocked the loop but next beta it will switch to aiohttp which should fix the event loop blocking. Its not the culprit for the ClientSessions though since it was using httpx before
Roger that! Thanks