500 error on upload from Github Actions?

Support Bug Fixes
1

Description

I’m getting back a 500 error when attempting to update the Coverage.jl uploader to be run on Github Actions

Commit SHAs

n/a

Repository

CI/CD or Build URL

Uploader

Coverage.jl

Codecov Output

[ Info: Submitting data to Codecov...
ERROR: LoadError: HTTP.ExceptionRequest.StatusError(500, "POST", "/upload/v2?branch=jn/github-actions&pull_request=307&service=github-actions&build=677392535&commit=81d0ff9f9b9eb7ba93902b249ef8d8655120ad11&slug=JuliaCI/Coverage.jl&build_url=https://github.com/JuliaCI/Coverage.jl/actions/runs/677392535&", HTTP.Messages.Response:
"""
HTTP/1.1 500 Internal Server Error
server: envoy
date: Mon, 22 Mar 2021 20:36:42 GMT
content-type: application/json
x-frame-options: DENY
content-length: vary: Origin, Cookie
x-content-type-options: nosniff
referrer-policy: same-origin
x-envoy-upstream-service-time: Via: 1.1 google
Alt-Svc: clear

{"error": "Server Error (500)"}""")

Expected Results

The coverage data would be uploaded, or an error message given stating the issue (missing token? bad url syntax? missing parameter?)

Actual Results

An internal server error was reported without details

Additional Information

I think most users now use the github codecov/codecov-action@v1 script, but I still wouldn’t have expected a 500 error when running this. It doesn’t tell me how to fix the uploader to make the server happy, so hoping for insights here.

2

I think I found the issue, following a hunch from another issue that a user had reported: the Accept header used to be required and allowed choosing the content type of the reply, and that is now rejected.

3

@vtjnash are you able to use the bash uploader to unblock you?

4

Not really. I’m doing maintenance work for a particular upload tool for the codecov community—I can’t really do that by using a different tool.

5

@vtjnash ahhh I see, apologies I read this issue wrong. Do you mind pushing a new commit up? I’d like to see what might be going on on our side and confirm it’s the Accept header.

6

I realized it still seemed to fail after removing that. Here’s a new run, still showing “500 Internal Server Error”:

7

@vtjnash we made some fixes on our side and I opened up a test PR here. Is this still an issue for you?

8

Thanks, it looks like it is working now! I’ve pushed a new commit to trigger it: https://codecov.io/gh/JuliaCI/Coverage.jl/commit/c0abb4bd9ffc5ebddf9856011aa2fd8957a190bd

It seems like now I’m hitting a couple other issues. The webhook isn’t reporting status completion, so I tried to reset it, but it errors that it can’t fix the webhook because it is broken(!):
image

And secondly, when I click the codecov logo on that page:
image

It tries to go to https://codecov.io/gh/JuliaCI/Coverage.jl/commit/c0abb4bd9ffc5ebddf9856011aa2fd8957a190bd/gh, which gives a 404 error.

Thanks again!

9

Hi @vtjnash, we made a fix for the logo on the page, is it still happening for you? Also, are you still seeing the webhook issue?

10

No, that link seems to still be trying to go to a nonsensical href (note that I need to be logged in, or it goes to a help page):
image

Yes, the webhook seems to be fixed now. It looks like the button to reset the webhook is gone. And the webhook itself seems to be working now when I pushed a new PR commit.

11

@vtjnash, ok, I think the logo should be good now. Would you be able to see if you’re still having the issue?

12

Yes, seems to be a valid link now. Thanks!

1 Like