[APICORE-980] Propagate gdal error messages instead of completely obfuscating them #6
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.
This is an initial draft PR to discuss the change.
We initially did not want to rely on string messages to determine 404 errors, But I think this will be an improvement for API consumer . This will allow us to determine if the file is actually missing in s3 and return a 404.
if we want to remain 100% backwards compatible, we can create a new function and leave the current
gdal.Open
as is.The new function can be used in sourcephotos:
Some example outputs:
For 404:
Couldn't resolve host:
I was messing around and added "xx" to the URL
This was in the logs when I enabled full verbose GDAL logs: