This repository was archived by the owner on May 21, 2025. It is now read-only.
Update readme with 400 error info #268
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #268 +/- ##
=====================================
Coverage 88% 88%
=====================================
Files 2 2
Lines 9 9
=====================================
Hits 8 8
Misses 1 1 |
thomasrockhu
approved these changes
Jun 2, 2020
Contributor
|
We started to encounter the same issue a couple of days ago and I can confirm the last version fixes it 👍 On that note, I believe it would be a good idea to update |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The latest release of codecov-python includes changes to resolve a specific 400 error while uploading to s3 (mentioned here). This PR updates the readme to encourage users to make sure they have the latest version of the package if they encounter 400 errors during upload - while they could be running into 400 errors for an entirely different reason than those addressed in the latest release, updating and seeing if that resolved the issue is generally a good first step to try here.
Happy to change the wording around, just let me know what y'all would prefer.