getter: get: raise exception for http errors in file_cache#74
Merged
Conversation
Member
Author
|
@R2ZER0 before going ahead with the task, I wanted to double check that this is the right aproach. |
Member
|
Issue #37 was more about reducing the noise in the datastore log (and triggering the monitoring) from http exceptions caused by unsuccessful fetches by ensuring that they are handled. The full backtrace of an exception from requests can be quite long. e.g. fetching an invalid url: https://wefwefwef.example.com/test can fill the log with [1] , whereas with the datagetter we know this is a case/scenario we normally handle and therefore isn't an application error. [1] |
e78a02b to
fcb512d
Compare
Member
Author
|
@michaelwood thanks for your comment. Let's see if what I have done now is better. |
fcb512d to
e92b14f
Compare
08f915d to
92fa45e
Compare
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
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.
related to #37