Commit creating failed: {"error": "Server Error (500)"}

[Andrew-S-Rosen]

As shown in this GitHub Actions report, I am receiving a Commit creating failed: {"error": "Server Error (500)"} when using codecov/codecov-action@v4 with v0.4.6. The full traceback is:

Traceback (most recent call last):
  File "codecov_cli/main.py", line 81, in <module>
  File "codecov_cli/main.py", line 77, in run
  File "click/core.py", line 1157, in __call__
  File "click/core.py", line 1078, in main
  File "click/core.py", line 1688, in invoke
  File "click/core.py", line 1434, in invoke
  File "click/core.py", line 783, in invoke
  File "click/decorators.py", line [33](https://github.com/Quantum-Accelerators/quacc/actions/runs/7831788227/job/21369356501#step:4:34), in new_func
  File "codecov_cli/commands/commit.py", line 64, in create_commit
  File "codecov_cli/services/commit/__init__.py", line [39](https://github.com/Quantum-Accelerators/quacc/actions/runs/7831788227/job/21369356501#step:4:40), in create_commit_logic
  File "codecov_cli/helpers/request.py", line 133, in log_warnings_and_errors_if_any
NameError: name 'exit' is not defined

I am using a token provided in a secret, but this error report is from an external contributor submitting a PR to the main branch. Here are the GitHub Actions steps for calling the codecov action.

[lbianchi-lbl]

Can confirm that we're also seeing a similar issue:

From a quick search, it seems the exception could be related to codecov/codecov-cli#370 and codecov/codecov-cli#371, with the underlying 500 server error being a separate issue.

If that's the case, and this is a failure in the server-error-handling code of codecov-cli, does it imply that that part of the codecov-cli code is... not covered by tests? (apologies for the low-hanging "isn't that ironic" remark)

[AlexSkrypnyk]

@thomasrockhu-codecov
There are 2 types of issues in the queue related to v4: the missing token ones and the ones like this where the response from infra is 500 or some other infra issue.

How can we use this product if it affects our development workflow?

Could you please provide some information on what Codecov is intended to do with these issues.

https://status.codecov.com/ shows that everything is working correctly, but we see otherwise.

Thank you

[thomasrockhu-codecov]

@Andrew-S-Rosen @lbianchi-lbl sorry for taking so long to get back to you, I believe we have fixed the initial exit issue you mentioned so closing out

@AlexSkrypnyk thank you for continuing to use Codecov. I know that we have had some stumbling blocks with the v4 release, but we have fixed a lot of the issues that are outstanding. If you are still running into issues, please open a new issue.