Error 500 when accessing settings of Bitbucket repository

Description

When trying to access my Codecov.io repository (which is hosed on Bitbucket), I get a HTTP 500 error.

Commit SHAs

The last coverage commit was 54f4e2a5c16ab396422d5590fe5115c4c010a38c.

Repository

The repository is: https://bitbucket.org/Roberto-R/uptime-tester

CI/CD or Build URL

Build is done from Bitbucket pipelines: https://bitbucket.org/Roberto-R/uptime-tester/addon/pipelines/home#!/results/24

Uploader

The bash uploader is being used. The most recent upload exited successfully.

Codecov Output

`                              Bash-20201130-cc6d3fe`

``

``

`==> Bitbucket detected.`

`    project root: .`

`--> token set from env`

`    Yaml not found, that's ok! Learn more at http://docs.codecov.io/docs/codecov-yaml`

`==> Running gcov in . (disable via -X gcov)`

`==> Searching for coverage reports in:`

`    + .`

`    -> Found 1 reports`

`==> Detecting git/mercurial file structure`

`==> Reading reports`

`    + ./coverage.xml bytes=71895`

`==> Appending adjustments`

`    https://docs.codecov.io/docs/fixing-reports`

`    + Found adjustments`

`==> Gzipping contents`

`        8.0K	/tmp/codecov.kJPjE1.gz`

`==> Uploading reports`

`    url: https://codecov.io`

`    query: branch=master&commit=54f4e2a5c16ab396422d5590fe5115c4c010a38c&build=24&build_url=&name=&tag=&slug=Roberto-R%2Fuptime-tester&service=bitbucket&flags=&pr=&job=24&cmd_args=`

`->  Pinging Codecov`

`https://codecov.io/upload/v4?package=bash-20201130-cc6d3fe&token=secret&branch=master&commit=54f4e2a5c16ab396422d5590fe5115c4c010a38c&build=24&build_url=&name=&tag=&slug=Roberto-R%2Fuptime-tester&service=bitbucket&flags=&pr=&job=24&cmd_args=`

`->  Uploading to`

`https://storage.googleapis.com/codecov/v4/raw/2020-12-14/BBA0BAA218E1E4884DD62E51758884C6/54f4e2a5c16ab396422d5590fe5115c4c010a38c/4d8f8655-f9af-4bf3-a127-a6ee0898fe07.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GOOG1EQX6OZVJGHKK3633AAFGLBUCOOATRACRQRQF6HMSMLYUP6EAD6XSWAAY%2F20201214%2FUS%2Fs3%2Faws4_request&X-Amz-Date=20201214T070425Z&X-Amz-Expires=10&X-Amz-SignedHeaders=host&X-Amz-Signature=5b2f654259847a1112c9794614849cd0a9373ec7b4019d04f6928a1b4428d0d0`

`  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current`

`                                 Dload  Upload   Total   Spent    Left  Speed`

``

`  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0`

`100  7469    0     0  100  7469      0  42437 --:--:-- --:--:-- --:--:-- 42437`

`    -> View reports at https://codecov.io/bitbucket/roberto-r/uptime-tester/commit/54f4e2a5c16ab396422d5590fe5115c4c010a38c`

Expected Results

Expected to view the repository settings.

Actual Results

Received HTTP 500 error page.

Additional Information

@RobertoRoos, are you trying to view this URL https://codecov.io/bitbucket/roberto-r/uptime-tester/commit/54f4e2a5c16ab396422d5590fe5115c4c010a38c or https://codecov.io/bb/Roberto-R/uptime-tester/?

What happens if you do not log in and view it on a private browsing session/incognito?

Both those URLs work. But if I access the repository main page and go to the settings tab (so https://codecov.io/bb/roberto-r/uptime-tester/settings) I am met with the 500 error.

The same happens from incognito mode.

I tried to link a repository in a new Bitbucket account to Codecov.io and I ran into the same issue there.

@RobertoRoos, can you try clearing your cookies, logging out, and logging back in again?

Tried it, but no changes.
I also logged in from a private window, still the 500 error.

Note that I also cannot view Commits, Branches and Pulls windows. They all give the same 500 error.

EDIT: Interesting, I can view the commits page from an incognito window (https://app.codecov.io/bb/roberto-r/uptime-tester/commits?page=1), but I cannot after I’ve logged in.

Error still persists, but I found out I can circumvent it by going directly to the settings/badge page: https://codecov.io/bb/roberto-r/uptime-tester/settings/badge

From the settings/badge page, I can click on the sidebar link to go to settings/general. So I’ve managed to extract my token, badge URL and re-create the webhook.

Not much as a solution I guess, but a workaround.