This PR includes the following proposed change(s):
DF-2301
Fixed the issue with not catching/logging the error when a request is being made to VIPS WS and it returns API related error.
Added proper exception catch block and logger to capture the error details when VIPS WS responds with an error including 500.
Type of change
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Setup VIPS WS base url to point to a dummy service that returns 500 error as response and confirmed that the error has been caught through the request's catch block and logged into an error log with detailed error message.
Checklist:
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[x] New and existing unit tests pass locally with my changes
Description
This PR includes the following proposed change(s):
Type of change
if your change is a breaking change, please add
breaking changelabel to this PRHow Has This Been Tested?
Setup VIPS WS base url to point to a dummy service that returns 500 error as response and confirmed that the error has been caught through the request's catch block and logged into an error log with detailed error message.
Checklist: