#1869 Ignore the ``No Content-Type`` error raised by pygit2
Merged by pingou. Opened by pingou.
ignore_no_header  into  master

Download 1869.patch

We recently starting running into this error for remote PR opened from a
github git repo. Maybe something change in github that is now triggering
this.
Anyway, with this commit, we will now be ignoring that specific error
and keep on going as usual.
It will at least allow accessing pull-requests that have already been
open and which are basically still valid.

Fixes https://pagure.io/pagure/issue/1863

Are you sure the 'N' in 'No Content-Type header in response' is capital because: https://github.com/libgit2/libgit2/blob/a6d833a29e100cae66d5144367e9102d093d4dbd/src/transports/http.c#L438

@vivekanand1101 the version we're using doesn't have: https://github.com/libgit2/libgit2/commit/909d5494368a00809bc42f4780e86f4dd66e4422#diff-9a42dd5d4d53ec9a60139b1911040470L438

cool :thumbsup:

I'm having an idea to be on the safe side :)

1 new commit added

  • Ignore case when checking the GitError raised

:thumbsup:

rebased

Thanks for the review :)

Pull-Request has been merged by pingou

Metadata