You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit improves error reporting on the client side. It propagates
some errors which were previously only captured on the server side.
In particular, it will now:
- report which property was being resolved, instead of showing
internal `auto.test.resources` properties
- capture errors which are sent by the server but were dropped
because of lack of JSON error handling
- report when a container cannot be started or failed during
startup
- provide clearer message when the test resources service is
down
Fixes#444
* Propagate more errors to the client side
This commit improves error reporting on the client side. It propagates
some errors which were previously only captured on the server side.
In particular, it will now:
- report which property was being resolved, instead of showing
internal `auto.test.resources` properties
- capture errors which are sent by the server but were dropped
because of lack of JSON error handling
- report when a container cannot be started or failed during
startup
- provide clearer message when the test resources service is
down
Fixes#444
* Apply suggestions from code review
Co-authored-by: Álvaro Sánchez-Mariscal <[email protected]>
---------
Co-authored-by: Álvaro Sánchez-Mariscal <[email protected]>
Feature description
Currently client side errors are something like ${auto.test.resources.datasources.default.url} cannot be resolved.
We should improve these errors somehow to indicate why:
The text was updated successfully, but these errors were encountered: