-
Notifications
You must be signed in to change notification settings - Fork 119
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
Response object parsing assumes presence of certain keys #320
Comments
Confirmed, I'm seeing these both too and using get fixes the problem for now. |
I'm seeing a similar issue with the 'invite' key:
|
It is causing since 1.38 version of synapse. There is also a issue reported with HomeAssistant home-assistant/core#53218 Is this a synapse error or a client implementation that needs to be changed? |
@begincalendar Looks like the fix is merged into master see #321 now it needs a release. |
Thanks for your patience everyone. v0.4.0 of matrix-python-sdk is now up with the fix: https://github.com/matrix-org/matrix-python-sdk/releases/tag/v0.4.0. Please upgrade when you can :) |
Describe the bug
I'm running HomeAssistant with the Matrix integration and I started seeing the following stack trace pop in my log file:
Having a brief look at the code in this repo, it appears as though there are many cases where keys in the response object are assumed to always be present.
I changed the dictionary lookups with
.get()
calls and that seemed to fix the issue.To Reproduce
Unfortunately I don't have a set of steps to reproduce this, it just cropped up.
Expected behavior
More robust parsing of response objects.
The text was updated successfully, but these errors were encountered: