Multiple SVN Branches seems to break Trac

[wrochow@…]

We have been using Trac successfully for several months now. We are a small team, and just now started using Branches in SVN. One of our developers just created and committed code from a second concurrent branch in Subversion.

As soon as he did that, we can no longer access Trac. Cannot login, or access any of the services.

It would seem to me that if something breaks in one of the modules, the others should continue to work.

I will try synchronizing Subversion, and report back on my success, but I wanted to capture this Trackback.

---

Python Traceback

Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 387, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 191, in dispatch
    chosen_handler = self._pre_process_request(req, chosen_handler)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 263, in _pre_process_request
    chosen_handler = f.pre_process_request(req, chosen_handler)
  File "/usr/lib/python2.4/site-packages/trac/versioncontrol/api.py", line 73, in pre_process_request
    self.get_repository(req.authname) # triggers a sync if applicable
  File "/usr/lib/python2.4/site-packages/trac/versioncontrol/api.py", line 101, in get_repository
    repos = self._connector.get_repository(rtype, rdir, authname)
  File "/usr/lib/python2.4/site-packages/trac/versioncontrol/svn_fs.py", line 260, in get_repository
    crepos = CachedRepository(self.env.get_db_cnx(), repos, None, self.log)
  File "/usr/lib/python2.4/site-packages/trac/versioncontrol/cache.py", line 34, in __init__
    self.sync()
  File "/usr/lib/python2.4/site-packages/trac/versioncontrol/cache.py", line 100, in sync
    (str(current_rev), path, kind, action,
  File "/usr/lib/python2.4/site-packages/trac/db/util.py", line 50, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
  File "/usr/lib/python2.4/site-packages/trac/db/sqlite_backend.py", line 56, in execute
    args or [])
  File "/usr/lib/python2.4/site-packages/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

[wrochow@…]

Synchronizing Subversion had no effect.

I am unable to use Trac at all right now. Any advice regarding a work around… (perhaps shutting down the "Browse Source" or something) would be greatly appreciated.

Thanks, Waldo

[wrochow@…]

Fixed

The problem was solved by running trac-admin and resync.

Perhaps future versions of Trac might be able to detect this lack synchronization, and provide a more useful error message.

Keep up the good work!

Man, I just love this software!

Waldo

[hyuga <hyugaricdeau@…>]

Hrm…what exactly do you mean when you started using branches in SVN?

Subversion doesn't have a built-in notion of a "branch" like CVS. Branching in SVN is just a copy operation on the tree you want to branch off from—Trac handles this fine so far as I've seen. This operation should update the revision number of the repository, so I'm not sure how you ended up with a duplicate key in the node_change table…

[Christian Boos]

Thanks for raising the attention on this ticket again: we once had a similar report that could be related to a subtle bug in the changeset code. In order to understand what's going on, we need the output of svn log -v -rXYZ where XYZ is the changeset that can't be synchronized (run a trac-admin $TRAC_ENV resync resync with the TracLogging set at DEBUG level).

[Christian Boos]

Duplicate of #4586. This kind of issues are fixed in 0.10.4, please upgrade.