-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
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
Detected blocking call inside the event loop #133965
Detected blocking call inside the event loop #133965
Comments
Hey there @hunterjm, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) xbox documentation |
@hunterjm I raised a PR for the underlying library that will allow us to pass in an SSLContext. This won't directly fix the issue, we need to change: As well, which I have a PR ready to go for once a new version of the library is cut. |
Hmm, ideally we use our own httpx client rather than theirs. But they expect a signed session and have that extended rather than wrapped |
Agreed, but like you said, not the way the library is written. If you check the AuthenticationManager, it seems to have been an intentional change:
So my thought was, short of drastic changes to the library (that I don't even know if the author will accept -- this seems to be used by a lot more than just HA), this was a simple fix that at least eliminates the blocking IO and eliminates creating an extra SSL context. |
My PR to the upstream library hasn't been reviewed yet so I don't think this is going to make it into the 2025.1 milestone |
I'm also experiencing this. I've manually updated the file xbox/webapi/common/signed_session.py on my installation to include this commit, however this didn't solve the warning message in the logs. |
You can’t just overrwrite the file. Every time you run HA it’s going to overwrite your manual change with the original |
The changes I've made appear to have persisted a HA OS reboot. but I understand this is not the proper way to do these things. |
Ok. As I mentioned though, that PR won’t fix the issue anyway. It adds the ability to fix it in HA but an HA change is needed. I can’t do that till the library pr is merged |
I think it would work if we create the SignedSession in the executor I think. But ideally we pass in our own httpx client to the library |
We may have to go the executor route if we want this fixed, the library author still hasn't responded to my PR. |
The problem
hello
received this log upon updating to 2025.1.0b2
thanks
What version of Home Assistant Core has the issue?
2025.0.0b2
What was the last working version of Home Assistant Core?
not sure
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: