Cannot fetch user based on address in paratii config

[bent0b0x]

Problem
This line is supposed to get us the user object, including things like username (which is important for saving usernames on videos when you publish).

However, this promise always resolves with null even when passing the address currently stored in paratii.eth.getAccount() (at least in my repeated testing today).

Perhaps @geckoslair or @jellegerbrandy know what might be going wrong?

[bent0b0x]

I dit a bit more investigation, and the reason this was not working is because the paratii.users.create promise is taking ~30 seconds or more to resolve (at least locally), implying that the user can take that long to be created. Thoughts on why this might be the case?

[bent0b0x]

FYI I can still reproduce this consistently locally. I have secured my account, but whenever I load the app and enter my password paratii-js cannot load my user.

To reproduce, set a breakpoint on this line and it is never hit, beacuse user is always null here.

I also see that updating username and email, at least locally, does not persist. I have the db running seemingly fine.

[jellegerbrandy]

Ok, this needs to be resolved, maybe we can do a session together with a screen share to see what is happening on yr machine

…

On Wed, May 30, 2018 at 2:11 AM Ben ***@***.***> wrote: FYI I can still reproduce this consistently locally. I have secured my account, but whenever I load the app and enter my password paratii-js cannot load my user. To reproduce, set a breakpoint on this line <https://github.com/Paratii-Video/paratii-portal/blob/dev/src/scripts/actions/UserActions.js#L100> and it is never hit, beacuse user is always null here. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#582 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABPuPTOO5JyJlR9kC-beruguHfaNWRb2ks5t3eO-gaJpZM4UAc7d> .

[bent0b0x]

I now have another concerning issue. Every time I try to save user data via paratii.users.upsert() I get this in the db logs, and the db crashes:

/Users/benjaminbaum/Desktop/dev/paratii-db/node_modules/mongoose/lib/utils.js:429
        throw err;
        ^
MongoError: E11000 duplicate key error collection: test.users index: username_1 dup key: { : null }
...

[jellegerbrandy]

@geckoslair , do you have a quick fix for the error?

[geckoslair]

run db.users.dropIndexes() 2018-06-01 11:31 GMT+02:00 Jelle <notifications@github.com>:

…

@geckoslair <https://github.com/geckoslair> , do you have a quick fix for the error? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#582 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEIeZd5UQUpitcZSMY5V4i6Fgj2MZeXJks5t4QnZgaJpZM4UAc7d> .

-- - - - - - - - - - - - - - - - - - - - - - - enrico cicconi | *p**iramid.studio* web piramid.studio skype <http://callto:eliawk/>geckoslair linkedin it.linkedin.com/in/*ecicconi* <http://it.linkedin.com/in/ecicconi> Information in this e-mail and any attachment is confidential and may be subject to legal privilege. If you are not the intended recipient please do not disclose, distribute, copy or use of the contents of the e-mail. Please delete it and any attachments and notify the sender that you have received the e-mail by error. Please consider the environment and don't print this e-mail unless you really need to.

[jellegerbrandy]

@bent0b0x , one possible explanation could have been that users.create did nto work because the transaction was not set unsigned (in that case, parity will wait for you to sign it in the UX). I did some refactoring in paratii-js that makes this situation less likely, let me know if it helps...

[bent0b0x]

Sounds like that could be it. Is this change on dev? Either way I’ll test soon locally!

[geckoslair]

still have this issue?

[bent0b0x]

Yes, this is happening on staging.

Steps to reproduce:
- fresh portal page
- create new account, finish flow in the modals
- go to profile page

You'll see no username in the profile, and this is because the user is coming back as null via paratii-js

I think I have figured out the issue.

@geckoslair, does the db enforce that usernames be unique? If so, this doesn't seem to be surfaced via paratii-js. If you try to save a non-unique username, paratii-js throws no error. However, the account is not created.

We should fix this, meaning we need an explicit error code of some sort if a username is already taken so that we can show messaging in the UI and try to create the account again.

[bent0b0x]

Created this issue in paratii-js