IntegrityError: duplicate key value violates unique constraint "hint_hintuse_hint_id_team_id_a08fcf36_uniq"

[sentry-io]

Sentry Issue: BACKEND-31

UniqueViolation: duplicate key value violates unique constraint "hint_hintuse_hint_id_team_id_a08fcf36_uniq"
DETAIL:  Key (hint_id, team_id)=(4, 224) already exists.

  File "django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "newrelic/hooks/database_psycopg2.py", line 64, in execute
    return super(CursorWrapper, self).execute(sql, parameters, *args,
  File "newrelic/hooks/database_dbapi2.py", line 38, in execute
    return self.__wrapped__.execute(sql, parameters,
  File "django_prometheus/db/common.py", line 71, in execute
    return super().execute(*args, **kwargs)

IntegrityError: duplicate key value violates unique constraint "hint_hintuse_hint_id_team_id_a08fcf36_uniq"
DETAIL:  Key (hint_id, team_id)=(4, 224) already exists.

(26 additional frame(s) were not displayed)
...
  File "django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "newrelic/hooks/database_psycopg2.py", line 64, in execute
    return super(CursorWrapper, self).execute(sql, parameters, *args,
  File "newrelic/hooks/database_dbapi2.py", line 38, in execute
    return self.__wrapped__.execute(sql, parameters,
  File "django_prometheus/db/common.py", line 71, in execute
    return super().execute(*args, **kwargs)

[jchristgit]

This is the case where a team has already used a specific hint, right? How would using a hint twice work? Maybe this is ap problem in the frontend?

[0xAda]

I believe this is caused by frontend not updating when someone uses a hint

…

On Sat, 9 Oct 2021, 17:24 Johannes Christ, ***@***.***> wrote: This is the case where a team has already used a specific hint, right? How would using a hint twice work? Maybe this is ap problem in the frontend? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#195 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACBCZQ3CJXFAY5HLR4DYBHDUGBUCDANCNFSM5FVGJC5A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[jchristgit]

Thanks, Ada.

@Bentechy66 could you confirm whether this is a frontend issue? Or should we handle this in backend?

[0xAda]

we probably do need to send a websocket notification when someone uses a hint if we dont already, and it probably should be a 4xx error rather than stacktracing