-
Notifications
You must be signed in to change notification settings - Fork 462
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
Xmltodict 0.13.0 likely broken (or moto use of it) #297
Comments
Please send a pull request with a new test case that exercises this failure in xmltodict. |
I am unable to - without a lot of investigation. With this issue I just wanted to let you that there is a potential bug in there.I just pinned xmltodoc to 0.12.0 in Airflow and maybe we are going to investigate further (but we have 70 providers and ~600 dependencies in Airflow - this is just one of transitive dependencies of our dependencies., so I am not sure if we can investigate all such issues down to a test case. Fine if you close it - it makes no difference to us as we simply pin our dependenceis there. Hopefully it will not bite you back. or maybe someone will investigate it and you will get it fixed.. For me - I just warned you, you can close the bug, no problem (or rather - it's likely still your problem, but not ours for now).. |
Moto maintainer here - the failure was due to the In case anyone else runs into this, we fixed this on our end in getmoto/moto#5111. Moto >= 3.1.9.dev3 should be fully compatible with xmltodict 0.13.0. |
I just tripped over this as well - in case it's helpful to anyone else, here's how I'm addressing it : pulp/pulp_rpm#2520 |
The XMLtodict 0.13.0 is likely broken (or moto use of it)
We have a sophisticated test harness in Airlfow where we run our tests for latest releases of our dependencies and it caught a strange eror.
I investigated it and traced it to xmltodict 0.13.0 upgrade.
I am not 100% sure whether it's the xmltodict or the way how boto/moto uses it but wanted to give an early warning in case you can investigate it faster.
The problem is that we are starting to ge "ValueError Malformatted input" when 0.13.0 is installed in some of our Amazon EMR tests:
The error is thrown in moto in this part of the code:
It's rather easy to reproduce:
pipx install -e ./dev/breeze
) - airflow development environmentbreeze
- this will pull and build the docker image that has all necessary depspip freeze | grep xmltodict
- see that 0.12.0 version is installedpytest tests/providers/amazon/aws/hooks/test_emr.py
-> they shoudl succedpip install xmltodict==0.13.0
pytest tests/providers/amazon/aws/hooks/test_emr.py
-> they shoudl fail with the "Malformed input"Once again 0 I am not sure if the root cause is moto/boto use of xmltodic or xmltodict itself, but I decided to open issues in both - maybe you can investigate and fix the root cause quicker.
Related: apache/airflow#23576
Related: getmoto/moto#5112
The text was updated successfully, but these errors were encountered: