# Unknown Error 500

**URL:** <https://community.codecov.com/t/unknown-error-500/1006>\
**Category:** Bug Fixes\
**Created:** [February 13, 2020, 9:57am UTC](https://community.codecov.com/t/unknown-error-500/1006 "2020-02-13T09:57:57Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![mofr](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/mofr/32/30_2.png) [@mofr](https://community.codecov.com/u/mofr)\
**Post date:** [February 13, 2020, 9:57am UTC](https://community.codecov.com/t/unknown-error-500/1006/1 "2020-02-13T09:57:57Z")

</div>

### Description

I see Unknown error 500 when opening pull request

> **[Code coverage done right.](https://app.codecov.io/gh/SupplyShift/net.supplyshift.server/compare/2439)**
>
> Hosted coverage report highly integrated with GitHub, Bitbucket and GitLab. Awesome pull request comments to enhance your QA.

or trying to open file diff

> **[Code coverage done right.](https://app.codecov.io/gh/SupplyShift/net.supplyshift.server/compare/2439/diff?src=pr&el=tree)**
>
> Hosted coverage report highly integrated with GitHub, Bitbucket and GitLab. Awesome pull request comments to enhance your QA.

### Repository

> **[Code coverage done right.](https://app.codecov.io/gh/SupplyShift/net.supplyshift.server)**
>
> Hosted coverage report highly integrated with GitHub, Bitbucket and GitLab. Awesome pull request comments to enhance your QA.

### Steps to Reproduce

1. Click link

**Expected behavior:** Pull request is shown

**Actual behavior:** Error 500

**Flakiness?** All the time

### Versions

Ubuntu 16.04, Chrome browser

---

<div class="post-metadata">

**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\
**Post date:** [February 20, 2020, 3:05pm UTC](https://community.codecov.com/t/unknown-error-500/1006/3 "2020-02-20T15:05:55Z")

</div>

Hi @mofr

This is a known edge case where reports get corrupted in storage that we have prioritized to investigate.

As a workaround, uploading the report again should fix this.

---

<div class="post-metadata">

**Author:** ![lballabio](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/lballabio/32/573_2.png) [@lballabio](https://community.codecov.com/u/lballabio)\
**Post date:** [February 26, 2020, 9:21am UTC](https://community.codecov.com/t/unknown-error-500/1006/4 "2020-02-26T09:21:13Z")

</div>

I seem to be hit by the same (see [https://codecov.io/gh/lballabio/QuantLib/commits](https://codecov.io/gh/lballabio/QuantLib/commits)).  
Does a corrupted report affect all further uploads, or might future ones get processed correctly even if I don’t re-upload the lot of them? (It would require re-running CI.)

---

<div class="post-metadata">

**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\
**Post date:** [February 26, 2020, 1:21pm UTC](https://community.codecov.com/t/unknown-error-500/1006/5 "2020-02-26T13:21:26Z")

</div>

Hi @lballabio

A bad report will fail the upload, not all uploads for that commit. In this case you appear to be sending us `.github/workflows/coverage.yml`, can you try adding an ignore rule for this?

---

<div class="post-metadata">

**Author:** ![lballabio](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/lballabio/32/573_2.png) [@lballabio](https://community.codecov.com/u/lballabio)\
**Post date:** [February 26, 2020, 1:54pm UTC](https://community.codecov.com/t/unknown-error-500/1006/6 "2020-02-26T13:54:30Z")

</div>

That used to work until about a week ago, but yes, I can try that.

---

<div class="post-metadata">

**Author:** ![lballabio](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/lballabio/32/573_2.png) [@lballabio](https://community.codecov.com/u/lballabio)\
**Post date:** [February 26, 2020, 5:30pm UTC](https://community.codecov.com/t/unknown-error-500/1006/7 "2020-02-26T17:30:44Z")

</div>

Hmm, that didn’t go well (see [https://codecov.io/gh/lballabio/QuantLib/commit/5c14f63f17dcf27e254bab9e1674e55acde579e8](https://codecov.io/gh/lballabio/QuantLib/commit/5c14f63f17dcf27e254bab9e1674e55acde579e8)). I added `".github/**/*"` to the `ignore` section and renamed `coverage.yml` to `codecov.yml` for good measure. Do you see anything on your side? Also, is this thread the correct place for me to follow up (because the problem might be the same as the original poster) or should I open a new one? Thanks!

---

<div class="post-metadata">

**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\
**Post date:** [February 26, 2020, 5:38pm UTC](https://community.codecov.com/t/unknown-error-500/1006/8 "2020-02-26T17:38:44Z")

</div>

> [@lballabio](#):
>
> [5c14f63f17dcf27e254bab9e1674e55acde579e8](https://codecov.io/gh/lballabio/QuantLib/commit/5c14f63f17dcf27e254bab9e1674e55acde579e8)

Every 500 is different, probably a new thread, but lets stay here.

I think we timed out trying to process the upload, do you know the rough size? Also, if you are using the bash uploader, can you adding `-X fixes`, that may help.

Edit: `codecov.yml` needs to be in the repo root for us to detect and use it, btw. 🙂

---

<div class="post-metadata">

**Author:** ![lballabio](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/lballabio/32/573_2.png) [@lballabio](https://community.codecov.com/u/lballabio)\
**Post date:** [February 26, 2020, 5:51pm UTC](https://community.codecov.com/t/unknown-error-500/1006/9 "2020-02-26T17:51:00Z")

</div>

Running `find . -name *.gcov | xargs wc -l` gives me about 1M lines of gcov files. Most of the .gcov files are for system headers; I’ll try pruning them out with `-g`.

However, my CI uses your github action, not the bash uploader. Not sure how configurable that is?

The `codecov.yml` with your configuration is in the repo root dir. The one in `.github/workflows` is the GitHub Actions workflow.

---

<div class="post-metadata">

**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\
**Post date:** [February 26, 2020, 6:29pm UTC](https://community.codecov.com/t/unknown-error-500/1006/10 "2020-02-26T18:29:36Z")

</div>

I don’t think you can add that flag to the action. If you can get the uploads down to around 20-50mb, that would be helpful. If not, we may need to switch you out to the bash uploader (the action is a wrapper around it)

---

<div class="post-metadata">

**Author:** ![lballabio](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/lballabio/32/573_2.png) [@lballabio](https://community.codecov.com/u/lballabio)\
**Post date:** [February 27, 2020, 9:23am UTC](https://community.codecov.com/t/unknown-error-500/1006/11 "2020-02-27T09:23:45Z")

</div>

I tried a couple of runs locally with the bash uploader, with and without `-X fix`, and still no joy ([here](https://codecov.io/gh/lballabio/QuantLib/commit/384aa0f83d3b1f6ac85466fdf417cfb7888fbc8d) and [here](https://codecov.io/gh/lballabio/QuantLib/commit/cc8ebf095db01ad8fcb1a79afcbeefe1bbdab277)). If you see something strange on your side, I’m all ears. On my side, except for these last local tries, [the failed commits](https://codecov.io/gh/lballabio/QuantLib/commits) used the same CI script as in [the last successful run](https://codecov.io/gh/lballabio/QuantLib/commit/65867ab7c44419b69e40e553b41230744b83cff9). Thanks!

---

<div class="post-metadata">

**Author:** ![drazisil](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/drazisil/32/496_2.png) [@drazisil](https://community.codecov.com/u/drazisil)\
**Post date:** [February 27, 2020, 2:01pm UTC](https://community.codecov.com/t/unknown-error-500/1006/12 "2020-02-27T14:01:26Z")

</div>

![image](https://canada1.discourse-cdn.com/flex029/uploads/codecov/original/1X/36ced985fe7dbca7d46a235d0cb895b8bf2a6408.png)

GitHib says either you don’t have access, or the commit doesn’t exist.

commit `cc8ebf095db01ad8fcb1a79afcbeefe1bbdab277` seems to timed out again. After trimming what’s the rough size of the upload, do you know? You can add the `-d` flag to the bash uploader to dump the upload, instead of uploading it for troubleshooting.

If the first one was with `-X fixes` I would leave that in place and we can investigate why GitHub is giving us access errors.

---

<div class="post-metadata">

**Author:** ![lballabio](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/lballabio/32/573_2.png) [@lballabio](https://community.codecov.com/u/lballabio)\
**Post date:** [February 27, 2020, 2:31pm UTC](https://community.codecov.com/t/unknown-error-500/1006/13 "2020-02-27T14:31:24Z")

</div>

The one with the access problem - my bad. It was a local try and I ended up uploading the reports before pushing the commit to GitHub.

I’ll try a dump.

---

<div class="post-metadata">

**Author:** ![lballabio](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/lballabio/32/573_2.png) [@lballabio](https://community.codecov.com/u/lballabio)\
**Post date:** [February 27, 2020, 6:24pm UTC](https://community.codecov.com/t/unknown-error-500/1006/14 "2020-02-27T18:24:20Z")

</div>

The full dump is 28M in full, 27M with -X fix. The version I had uploaded with that commit, though, excluded .gcov files from std headers and was 18M uncompressed.

---

<div class="post-metadata">

**Author:** ![tom](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.codecov.com/tom/32/8_2.png) [@tom](https://community.codecov.com/u/tom)\
**Post date:** [May 22, 2020, 2:28am UTC](https://community.codecov.com/t/unknown-error-500/1006/16 "2020-05-22T02:28:28Z")

</div>

Hi @lballabio, I realize that it’s been an unacceptable long time hearing from us. I realize that you have since switched off of `Codecov`, but if you decide to use us again, I think you’ll be satisfied with the infrastructure changes we’ve made to support the large file uploads.
