You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently aiohttp has an unresolved bug due to which if any request throws 400 status code, the error message is not visible, the module itself passes self.status == 400 and self.reason == "BAD REQUEST", issue link for more details: aio-libs/aiohttp#4600.
This makes it difficult to debug a failed request from a user's perspective since the connector would only output Exception: Bad Request.
Problem Description
Currently
aiohttp
has an unresolved bug due to which if any request throws 400 status code, the error message is not visible, the module itself passesself.status == 400
andself.reason == "BAD REQUEST"
, issue link for more details: aio-libs/aiohttp#4600.This makes it difficult to debug a failed request from a user's perspective since the connector would only output
Exception: Bad Request
.Proposed Solution
Use the solution provided here aio-libs/aiohttp#4600 (comment) in our utils. (Tested it, working fine)
Alternatives
Wait till the official version is released supporting it (aio-libs/aiohttp#3892 had been merged more than a year ago in master branch)
The text was updated successfully, but these errors were encountered: