-
Notifications
You must be signed in to change notification settings - Fork 338
test_media_types_method - Test failure #547
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
Comments
From 2.3.5 changelog the culprit is likely: Improper Content-Length Parsing Werkzeug - 2716 test_media_types_method - can be fixedUpdating test_media_types_method to have q=0.5 instead of q=.5, fixes that test:
test_media_types_qThe 2nd test that fails is test_media_types_q, which also has q=.5. Changing that to 0.5 didn't fix it and it fails in a different way. The api.mediatypes() returns an empty list
|
@darless Thanks for bringing this to my attention and the suggested fixes. For some reason, I didn't get notified by the build system! I will try and get it patched tomorrow. :) |
Change in Werkzeug 2.3.5 as issued here caused the fail in build. As per HTTP RFC the quality-factor for HTTP Accept Header has to be like X.X. So changing them all to such format, all Unit tests and Tox test passes. Also posted a PR for review. :-) |
@chipndell Thanks for the PR, I never quite got the time to fix as I had planned! |
@peter-doggart No worries. I loved to work on it. Also please share if you have more cool features that needs to be implemented. Learning and looking forward. :-) |
Uh oh!
There was an error while loading. Please reload this page.
Latest github actions run with failure:
https://github.com/python-restx/flask-restx/actions/runs/5385063797/jobs/9773681086
Failure seen
Reproduce
Looks like all python versions are failing in the same way.
Expected Behavior
Tests expects to see mediatypes as both application/json and application/xml
Actual Behavior
Test only sees application/json
Environment
Additional info
Failure started about 3 weeks ago:
From what I can see nothing changed in the repo since March. Looking at the good run and the bad run, the only differences are:
Changing urllib to the old version didn't fix it.
Changing Werkzeug to the old 2.3.4 version fixed the failure.
Werkzeug 2.3.5 changlog: https://werkzeug.palletsprojects.com/en/2.3.x/changes/#version-2-3-5
The text was updated successfully, but these errors were encountered: