Unable to view any private repos

Description

I’m no longer able to view any of my private repos on Codecov. All of the entries below are for one of my private repos.

Commit SHAs

6187888f24b2f6d71b19a4c963fd80cf89c0a906

Repository

https://github.com/adamjstewart/eclipse

CI/CD or Build URL

https://github.com/adamjstewart/eclipse/actions/runs/665530135

Uploader

GitHub Actions

Codecov Output

Run codecov/codecov-action@v1
/usr/bin/bash codecov.sh -n  -F  -Q github-action

  _____          _
 / ____|        | |
| |     ___   __| | ___  ___ _____   __
| |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
| |___| (_) | (_| |  __/ (_| (_) \ V /
 \_____\___/ \__,_|\___|\___\___/ \_/
                              Bash-20210309-2b87ace


==> git version 2.30.2 found
==> curl 7.68.0 (x86_64-pc-linux-gnu) libcurl/7.68.0 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0 librtmp/2.3
Release-Date: 2020-01-08
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp 
Features: AsynchDNS brotli GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets
==> GitHub Actions detected.
    Env vars used:
      -> GITHUB_ACTIONS:    true
      -> GITHUB_HEAD_REF:   
      -> GITHUB_REF:        refs/heads/master
      -> GITHUB_REPOSITORY: adamjstewart/eclipse
      -> GITHUB_RUN_ID:     665530135
      -> GITHUB_SHA:        6187888f24b2f6d71b19a4c963fd80cf89c0a906
      -> GITHUB_WORKFLOW:   pytest
    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=46493
==> Appending adjustments
    https://docs.codecov.io/docs/fixing-reports
    -> No adjustments found
==> Gzipping contents
        4.0K	/tmp/codecov.oIdoaO.gz
==> Uploading reports
    url: https://codecov.io
    query: branch=master&commit=6187888f24b2f6d71b19a4c963fd80cf89c0a906&build=665530135&build_url=http%3A%2F%2Fgithub.com%2Fadamjstewart%2Feclipse%2Factions%2Fruns%2F665530135&name=&tag=&slug=adamjstewart%2Feclipse&service=github-actions&flags=&pr=&job=pytest&cmd_args=n,F,Q
->  Pinging Codecov
https://codecov.io/upload/v4?package=github-action-20210309-2b87ace&token=secret&branch=master&commit=6187888f24b2f6d71b19a4c963fd80cf89c0a906&build=665530135&build_url=http%3A%2F%2Fgithub.com%2Fadamjstewart%2Feclipse%2Factions%2Fruns%2F665530135&name=&tag=&slug=adamjstewart%2Feclipse&service=github-actions&flags=&pr=&job=pytest&cmd_args=n,F,Q
->  Uploading to
https://storage.googleapis.com/codecov/v4/raw/2021-03-18/210D36BC2E10A96966F60E5E1EFA0257/6187888f24b2f6d71b19a4c963fd80cf89c0a906/449985b4-9131-45ce-a4a2-3990a202530d.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GOOG1EQX6OZVJGHKK3633AAFGLBUCOOATRACRQRQF6HMSMLYUP6EAD6XSWAAY%2F20210318%2FUS%2Fs3%2Faws4_request&X-Amz-Date=20210318T182702Z&X-Amz-Expires=10&X-Amz-SignedHeaders=host&X-Amz-Signature=94710ccbead4be8b141f43f3ea925f3c42876b4299165d0a969c63724d749492
  % 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  3123    0     0  100  3123      0  18589 --:--:-- --:--:-- --:--:-- 18479
100  3123    0     0  100  3123      0  18589 --:--:-- --:--:-- --:--:-- 18479
    -> Reports have been successfully queued for processing at https://codecov.io/github/adamjstewart/eclipse/commit/6187888f24b2f6d71b19a4c963fd80cf89c0a906

Expected Results

I would expect to be able to view my project on Codecov. This has worked in the past, it just doesn’t work anymore.

Actual Results

I’m able to view Codecov, but I get a 404 error when trying to view Codecov.

Additional Information

Screen Shot 2021-03-18 at 1.49.47 PM

Hi @adamjstewart, sorry for the delay in responding here. Are you still running into this issue?