-
Notifications
You must be signed in to change notification settings - Fork 1
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
The "profileList" endpoint is not working. #36
Comments
Would be interesting to see the result from |
Hey, I initially reported this issue to msterle via discord.
First account is valid, the second one isn't |
Sorry for the delayed response @leonprou. Intitially I thought this was a problem with only the graphql api, but seems like it's a problem with |
@oed hey any update in this? |
Hey, @leonprou work on this has gotten a bit delayed. Yes it's related to 3box/3box-graphql#20 :) |
Edit oed, 2020-02-20
It seems like this error comes from the
profileList
endopint in 3box-api not working properly. Even calling this endpoint with only one address that has a proper profile this call stalls and eventually causes an error.Single missing profile when fetching multiple profiles through graphql causes the whole query to fail
@msterle commented on Mon Feb 10 2020
If one or more addresses aren't registered with the address server, the graphql endpoint correctly returns only those with existing profiles. However, if the address is registered with the server, but the profile doesn't exist, the graphql endpoint returns a 500 error.
Test query:
Is it possible this issue is linked to profiles that have been corrupted, and the error on those isn't being handled gracefully?
For example addresses, ping @msterle directly
The text was updated successfully, but these errors were encountered: