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
If the communication with the pact broker fails (in my case because I used the matching branch selector, but did not provide a provider branch name), the status code (in my case 400) is logged, but not the response body. Especially in 400 responses this would really simplify the debugging. Right now I have to set a breakpoint within pact to get the response body.
The text was updated successfully, but these errors were encountered:
Nvm. just took a further look around where RequestFailedException is used. Seems that it should be parsed and logged in case of 400 errors. Will further investigate, why I'm not seeing it.
If the communication with the pact broker fails (in my case because I used the matching branch selector, but did not provide a provider branch name), the status code (in my case 400) is logged, but not the response body. Especially in 400 responses this would really simplify the debugging. Right now I have to set a breakpoint within pact to get the response body.
The text was updated successfully, but these errors were encountered: