Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[ci] better errors on bad github response
Not sure what was wrong, but CI was getting 422s from GitHub. Using a `raise_for_status=True` ClientSession circumvented gidgethubs native error handling logic smothering the HTTP response body where github places critical debugging information. Aiohttp is aware that `raise_for_status` provides no access to the response body. They addressed this in https://github.com/aio-libs/aiohttp/pulls/3892, but that has not been released because 4.0.0 has not yet been released. Another relevant issue: aio-libs/aiohttp#4600.
- Loading branch information