-
Notifications
You must be signed in to change notification settings - Fork 31
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
failed to create user #16
Comments
@matthew-altman it looks like we are not de-serializing into the errors object on a non 2xx response. Can you take a look? @alonlong if you recreate using postman , insomnia or some rest client the JSON body response on a 400 will tell you what the validation error is that is causing the request to fail. |
@alonlong It looks like you're throwing away the |
@alonlong Were you able to resolve this issue? Or do you have any additional error messages for us? |
Pretty sure this is related to the issue I'm having currently. A request to CreateUser returns zero validation errors but err is equal to EOF. Any current work arounds? Happy to post any additional findings too. |
@abbottm-go if you try to make the same request using a REST client such as insomnia or postman what is the error and status code? If we can identify the actual error - then we should be able to recreate the scenario and symptom to resolve the core issue. Thanks! |
The status code is 200 when err is equal to EOF on the login function. That's using insomnia. This occurs with both the Login and CreateUser functions. using go 1.14.2 :) |
@robotdan
` the err object is the one defaulting to EOF & errors object is just an empty map |
Hi, This is my golang code:
uuid := id2uuid(id)
fmt.Println(uuid)
when I run this code, the result:
50166975-0100-0000-0516-796758492463
{"statusCode":400,"user":{}}
what's the problem?
The text was updated successfully, but these errors were encountered: