got an IntegrityError: columns rev, path, change_type are not unique

[piekarczyk - at - gmail.com]

I can't handle this problem. We have a dozen of projects already and everything works fine, but not this one.

Trac resync and svn restore didn't help.

Traceback (most recent call last):
  File "/var/lib/python-support/python2.4/trac/web/main.py", line 387, in dispatch_request
    dispatcher.dispatch(req)
  File "/var/lib/python-support/python2.4/trac/web/main.py", line 191, in dispatch
    chosen_handler = self._pre_process_request(req, chosen_handler)
  File "/var/lib/python-support/python2.4/trac/web/main.py", line 263, in _pre_process_request
    chosen_handler = f.pre_process_request(req, chosen_handler)
  File "/var/lib/python-support/python2.4/trac/versioncontrol/api.py", line 73, in pre_process_request
    self.get_repository(req.authname) # triggers a sync if applicable
  File "/var/lib/python-support/python2.4/trac/versioncontrol/api.py", line 101, in get_repository
    repos = self._connector.get_repository(rtype, rdir, authname)
  File "/var/lib/python-support/python2.4/trac/versioncontrol/svn_fs.py", line 260, in get_repository
    crepos = CachedRepository(self.env.get_db_cnx(), repos, None, self.log)
  File "/var/lib/python-support/python2.4/trac/versioncontrol/cache.py", line 34, in __init__
    self.sync()
  File "/var/lib/python-support/python2.4/trac/versioncontrol/cache.py", line 100, in sync
    (str(current_rev), path, kind, action,
  File "/var/lib/python-support/python2.4/trac/db/util.py", line 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
  File "/var/lib/python-support/python2.4/trac/db/sqlite_backend.py", line 56, in execute
    args or [])
  File "/var/lib/python-support/python2.4/trac/db/sqlite_backend.py", line 48, in _rollback_on_error
    return function(self, *args, **kwargs)
IntegrityError: columns rev, path, change_type are not unique

[Christian Boos]

I assume you're using 0.10.3.

If this error is fixed after a resync but reappears intermittently, then upgrading to 0.10.4 will help.

But if you're ending up with the above error after a resync, then it's another problem. In this case, if it's possible (small size, open source), can you provide us with a dump of the repo? Otherwise, you would have to run the resync at DEBUG log level and look at the latest successful revision resynced (say N), then show us the result of svn log -v -rN+1 (i.e. the one that can't be resynced).

[piekarczyk -at- gmail.com]

Well, I have a strange situation now.

Trac works fine. And I don't know what exactly helped.

I know that there were no problems with SVN, because programmers commited their work every day. They were only unable to use Trac.

I haven't mentioned that Trac's resync and SNV's restore hadn't helped because they'd showed nothing. They passed by without any problems.

Today I started my work with restarting apache. And after that I've found that Trac works. The problem is that I haven't checked if it works before restarting apache.

So now - if You still would like to take a look into the code, we can send You the source. Just let me know if You still treat it as a problem.

Thanks a lot for Your answer.

[Christian Boos]

Thank you for the feedback. No, we don't need your repository data, as resync didn't fail.

From what you described, this ticket is a duplicate of #4586. If you don't want the issue to reappear, you should upgrade to Trac 0.10.4.