[API] UNIQUE constraint failed error

[Aksh-Bansal-dev]

Steps to reproduce:

• Start API server using docker
• Click sign in on login page.

django.db.utils.IntegrityError: UNIQUE constraint failed: api_accounts_user.email
[11/Jul/2022 08:52:06] "POST /auth/token/ HTTP/1.1" 500 191429

[arminpatel]

Tried to reproduce the bug, but my login was successful.

My best guess is that the email of superuser (or some manually added user) and the google email was same and hence result in breaking of uniqueness. Can someone else confirm?

[Samy-33]

@Aksh-Bansal-dev, do you still face this issue? If yes, please do post the whole error that you get in the API console. It would probably a huge error message, you can paste it over: https://ctxt.io/ or some other pasting website online and share a link.

[Samy-33]

My best guess is that the email of superuser (or some manually added user) and the google email was same and hence result in breaking of uniqueness. Can someone else confirm?

That's correct but it shouldn't happen, if the user is already present they should be logged in instead of throwing this error.
It's weird that you're not getting this error but @Aksh-Bansal-dev is. Let's wait for @Aksh-Bansal-dev to give us more info. If it was a transient error, we could close this and reopen again when we face it.

[Aksh-Bansal-dev]

The ui sends 2 duplicate requests for the token, sometimes one of these requests returns 403.

[arminpatel]

The ui sends 2 duplicate requests for the token, sometimes one of these requests returns 403.

Got the same error when I restarted the container.

{'email': 'arminpatel5@gmail.com', 'first_name': None, 'last_name': None, 'picture_url': None} is user_info from

gymkhana/api/api/auth/views.py

Line 50 in 85b5b1d

user_info = self._extract_userdata_from_id_token(id_info)

[arminpatel]

Got the orignally posted error: error log
My guess is that two requests are being sent simultaneously and for both of them the new user doesn't exist and both try to create a new one resulting in an integrity error (Race condition?).

[Samy-33]

There are two possible solutions that I can think of right now:

• Use throttling to allow 1 request per client per second
• Handle django.db.utils.IntegrityError while creating a user.

There is one more issue though, sometimes it also throws 403 forbidden. Not sure why that's happening. We will wait and see if this causes more issues.