Skip to content
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

Closed
msterle opened this issue Feb 10, 2020 · 5 comments
Closed

The "profileList" endpoint is not working. #36

msterle opened this issue Feb 10, 2020 · 5 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@msterle
Copy link
Contributor

msterle commented Feb 10, 2020

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:

{"operationName":"Profiles","variables":{"accounts":["<address 1>", "<address 2>"]},"query":"query Profiles($accounts: [String]!) {\n  profiles(ids: $accounts) {\n eth_address\n    image\n   }\n}\n"}

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

@oed
Copy link
Member

oed commented Feb 11, 2020

Would be interesting to see the result from Box.getProfiles with the same array of addresses.

@leonprou
Copy link

Hey, I initially reported this issue to msterle via discord.
@oed calling Box.getProfiles you get the same 502 Bad Gateway, first the call is pending for some time, then you get the error.
You can try it with that body:

{"addressList":["0xD418c5d0c4a3D87a6c555B7aA41f13EF87485Ec6,""0x3e281e241dd27b81158f52ca124c339b3451988c"],"didList":[]}

First account is valid, the second one isn't

@oed
Copy link
Member

oed commented Feb 20, 2020

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 Box.getProfiles in general. I can't even fetch one profile with it. Bumping this up in our priority list.

@oed oed transferred this issue from 3box/3box-graphql Feb 20, 2020
@oed oed assigned zachferland and derrandz and unassigned zachferland Feb 20, 2020
@oed oed changed the title Single missing profile when fetching multiple profiles through graphql causes the whole query to fail The "profileList" endpoint is not working. Feb 20, 2020
@leonprou
Copy link

leonprou commented Mar 5, 2020

@oed hey any update in this?
Does this issue is related 3box/3box-graphql#20 ?

@oed
Copy link
Member

oed commented Mar 10, 2020

Hey, @leonprou work on this has gotten a bit delayed. Yes it's related to 3box/3box-graphql#20 :)
@jshrt can give you the latest updates.

@michaelsena michaelsena added this to the Sprint 37 milestone Mar 11, 2020
@michaelsena michaelsena added the bug Something isn't working label Mar 11, 2020
@msterle msterle closed this as completed Mar 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants