500 error on upload from Github Actions?

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.

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.

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

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.

@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.

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