You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I tired to setup the codecov cli to handle the report uploads. Unfortunately the token I had stored in Git secrets was either malformed or otherwise invalid. This was impossible to figure out, without going to the codecov logs. A customer wouldn't be able to decipher this on their own.
Describe the solution you'd like
Validate the token for UUID schema before sending "everything" to the server.
Describe alternatives you've considered
No other solutions were considered.
Additional context
Detailed recap.
I tried to pass in the token to the codecov cli, as described in the github docs. The output of the CLI in the CI showed that "some token" was available to proceed with the upload:
I interpreted the above output as though the token was accepted and parsed by the CLI.
However during upload we saw a 500 error, that is pretty generic. The only way to figure out what was caused by the malformed token was to look at the GCP logs. A customer would likely open a support ticket at this point.
A bonus here would be to return a message from the server that the 500 was caused by the "bad token".
This discussion was converted from issue #223 on January 10, 2024 16:51.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What product do you want to improve?
Codecov CLI
Is your feature request related to a problem? Please describe.
I tired to setup the codecov cli to handle the report uploads. Unfortunately the token I had stored in Git secrets was either malformed or otherwise invalid. This was impossible to figure out, without going to the codecov logs. A customer wouldn't be able to decipher this on their own.
Describe the solution you'd like
Validate the token for UUID schema before sending "everything" to the server.
Describe alternatives you've considered
No other solutions were considered.
Additional context
Detailed recap.
I tried to pass in the token to the codecov cli, as described in the github docs. The output of the CLI in the CI showed that "some token" was available to proceed with the upload:
I interpreted the above output as though the token was accepted and parsed by the CLI.
However during upload we saw a 500 error, that is pretty generic. The only way to figure out what was caused by the malformed token was to look at the GCP logs. A customer would likely open a support ticket at this point.
A bonus here would be to return a message from the server that the 500 was caused by the "bad token".
Beta Was this translation helpful? Give feedback.
All reactions