-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Payload with non serializable JSON data #138
Comments
Hello @ArturoQuintana, I was discussing with @cmagnobarbosa and we would like to get more information about failed test, like the output showing the error/exception. Can you share the output with us? We have some guess about why the test is failing and the output would help us understand better. Thank you. |
Hi @josemauro and @cmagnobarbosa, thanks for getting back to us about this issue. |
Thank you @ArturoQuintana. The error shown in the output is a TypeError raised because you are using an invalid dictionary that can not be serializable to JSON by 'json.dumps'. The method 'dumps' will only return you a string, so instead using 'dumps' in this case you can assemble your own string with the invalid JSON replacing |
Thanks @josemauro |
Sure, but this error is not related to the API call, actually you are not even making the call because a primary error is occurring preventing the call to be done. As I mentioned before, the error is caused by 'json.dumps'. I've tested the API call using the string that I recommended and I got the code 400. |
Hi, @cmagnobarbosa.
Issue 132 seems to be closed by PR 137, and in there, we referenced problems with some payloads.
The application continues failing in the case in which a payload specifies non-serializable JSON data.
some tests:
The text was updated successfully, but these errors were encountered: