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

PostgreSQL Error in email_hash table: "doppelter Schlüsselwert verletzt Unique-Constraint" #12937

Closed
2 of 7 tasks
somera opened this issue Sep 24, 2020 · 3 comments
Closed
2 of 7 tasks
Labels
issue/duplicate The issue has already been reported.

Comments

@somera
Copy link

somera commented Sep 24, 2020

  • Gitea version (or commit ref): 1.12.4
  • Git version: 2.25.1
  • Operating system: Ubuntu 20.04
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I'm mirroring a lot of GitHub projects. And in PostgreSQL logs I see this error:

2020-09-24 19:45:52.473 CEST [53703] gitea@giteadb DETAIL: Schlüssel »(hash)=(e3df20cd7a67969c41a65f03bea54961)« existiert bereits. 2020-09-24 19:45:52.473 CEST [53703] gitea@giteadb ANWEISUNG: INSERT INTO "email_hash" ("hash","email") VALUES ($1, $2) 2020-09-24 19:45:52.481 CEST [34263] gitea@giteadb LOG: Ausführen <unnamed>: INSERT INTO "email_hash" ("hash","email") VALUES ($1, $2) 2020-09-24 19:45:52.481 CEST [34263] gitea@giteadb DETAIL: Parameter: $1 = '5286ca631fff30960bfc2b337144556f', $2 = 'xx@xxxxxxx' 2020-09-24 19:45:52.481 CEST [34263] gitea@giteadb FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »email_hash_pkey«

Screenshots

@jolheiser
Copy link
Member

jolheiser commented Sep 24, 2020

Same issue as #12287

I believe this is fixed by #12577 and will be in 1.13.0

@jolheiser jolheiser added the issue/duplicate The issue has already been reported. label Sep 24, 2020
@somera
Copy link
Author

somera commented Sep 24, 2020

Same issue as #12287

I believe this is fixed by #12577 and will be in 1.13.0

Looks so. Is there an release date for 1.13.0?

@jolheiser
Copy link
Member

We are in feature freeze and trying to clean out final issues before getting an rc1 out the door. 🙂

https://github.com/go-gitea/gitea/milestone/67

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Development

No branches or pull requests

2 participants