There's been an error. Please try refreshing your browser, if this error persists

Before submitting a topic, please confirm the following

I have searched for similar issues before creating this topic.
I have verified that my repository is using the Codecov GitHub app, if using GitHub
I have validated my codecov.yaml configuration file.
I have filled out the below sections to the best of my ability.


Visiting the dashboard for our public github project fails since a couple of days

Looking at commits, settings etc works.


Latest upload for main branch

Codecov Output

Please provide the full output of running the uploader on your CI/CD. This will typically have the Codecov logo as ASCII.

  _____          _
 / ____|        | |
| |     ___   __| | ___  ___ _____   __
| |    / _ \ / _\`|/ _ \/ __/ _ \ \ / /
| |___| (_) | (_| |  __/ (_| (_) \ V /
 \_____\___/ \__,_|\___|\___\___/ \_/
==> Circle CI detected
x> No token specified or token is empty
==> Gzipping contents
==> Uploading reports
    query: token=secret&flags&package=ruby-0.6.0&service=circleci&build=94297&job=0&slug=openSUSE%2Fopen-build-service&pr&branch=master&commit=e27d1c2a2ee4bccc671c9bc6df6e273e982ebc87
->  Pinging Codecov
->  Uploading to$CREDENTIAL%2F20220902%2FUS%2Fs3%2Faws4_request&X-Amz-Date=20220902T082530Z&X-Amz-Expires=10&X-Amz-SignedHeaders=host&X-Amz-Signature=$SIGNATURE
    View reports at

Expected Results

The dashboard works.

Actual Results

The dashboard shows a message

There's been an error. Please try refreshing your browser, if this error persists please contact support.

Hi @hennevogel we made a quick fix to this so that you can see the repository page now.

Thank you @tom

Something is still off with it. As default branch or branch context I can only select branches that don’t exist anymore. Our default branch (master) is not in the selection at all.


Screenshot from 2022-09-06 12-55-37

with Branches · openSUSE/open-build-service · GitHub

bump @tom

not being able to view any (non-ancient) branches makes the app pretty unusable to us…

Hi @hennevogel sorry, I had forgotten to update here. The engineering team is currently working on the fix for this.

1 Like