Vote #73646
未完了ActiveRecord::RecordNotUnique for git repository
0%
説明
I've installed Redmine and linked it to a git repository that's been running development for a very long time (heavy, active development for about a year). Upon trying to load the Repository tab for the project I get an error. Here's the relevant section of the log:
Started GET "/redmine/projects/
Processing by RepositoriesController#show as HTML
Parameters: {"id"=>"fredchat"}
Current user: admin (id=1)
Completed 500 Internal Server Error in 912ms
ActiveRecord::RecordNotUnique (Mysql2::Error: Duplicate entry '1-2a5b30caa8969dded7f57c9cda5f914ea88ea29f' for key 'changesets_repos_rev': INSERT INTO changesets (comments, commit_date, committed_on, committer, repository_id, revision, scmid, user_id) VALUES ('Merge branch \'autoupdate\' of
app/models/repository/git.rb:222:in save_revision'block (2 levels) in save_revisions'
app/models/repository/git.rb:211:in
app/models/repository/git.rb:208:in block in save_revisions'each'
app/models/repository/git.rb:207:in
app/models/repository/git.rb:207:in save_revisions'fetch_changesets'
app/models/repository/git.rb:154:in
app/controllers/repositories_controller.rb:114:in `show'
journals
I've attached a patch that fixes this issue by prepending underscores to non-unique commit SHA-1s in a before_create handler
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
You're not supposed to have a duplicate SHA-1, do you know why you have this?
--------------------------------------------------------------------------------
SHA-1 is collision-resistant, but mathematically speaking there's no way it can be collision proof. In especially large datasets it's entirely possible for two checksums to be the same-look up the birthday problem.
--------------------------------------------------------------------------------
Scratch that, it actually looks like it's trying to overwrite the same revisions, so somewhere the check to see if a revision has already been inserted is failing.
--------------------------------------------------------------------------------
Are these really the same hash values?
It is very rare case on Mercurial *valid* repository.
http://mercurial.selenic.com/wiki/FAQ/TechnicalDetails
Redmine checks hash before inserting database.
source:tags/2.3.0/app/models/repository/git.rb#L167
So, "Not Unique" error does not happen on *single process*.
But, it happens on *multi processe*.
In this case, you can ignore it.
See #13086.
--------------------------------------------------------------------------------
I just ran into this issue. I fixed it by truncating the three 'changesets' tables in the redmine DB.
It can be caused by refreshing or making two requests to a new repository from redmine at once. The two requests run in parallel and cause each other to collide. Any attempt made after this occurs to access the repo fails as Redmine tries to insert everything anew rather than update the data in the database, causing more collisions.
Definately something that needs to be dealt with in the redmine code. I've learnt my lesson, but this could cause major issues with a busy redmine server.
--------------------------------------------------------------------------------
related_issues
relates,Needs feedback,13086,"Mysql::Error: Duplicate entry" in fetching revisions
relates,New,2824,MySQL Deadlock Error when showing a big repository