Add error message for non-200 status codes #17
Merged
Conversation
This file contains 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
sengi
approved these changes
Jun 27, 2024
If the request is not sucessful we confusingly get a time parse error (because there is no Last-Modified header and string to parse). This makes it more explicit when the exporter is failing due to a non-200 response.
theseanything
force-pushed
the
add-status-code-check
branch
from
0ba878f to
8e4e72e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If the request is not sucessful we confusingly get a time parse error (because there is no Last-Modified header and string to parse). This makes it more explicit when the exporter is failing due to a non-200 response.