id summary reporter owner description type status priority milestone component version severity resolution keywords cc branch changelog apichanges internalchanges 4043 two concurrent resync attempts can leave the database in an inconsistent state Christian Boos Christian Boos "If this happens, then the every further attempt fails with: {{{ Traceback (most recent call last): File ""/usr/lib/python2.4/site-packages/trac/web/main.py"", line 356, in dispatch_request dispatcher.dispatch(req) File ""/usr/lib/python2.4/site-packages/trac/web/main.py"", line 224, in dispatch resp = chosen_handler.process_request(req) File ""/usr/lib/python2.4/site-packages/trac/versioncontrol/web_ui/changeset.py"", line 206, in process_request chgset = repos.get_changeset(new) File ""/usr/lib/python2.4/site-packages/trac/versioncontrol/cache.py"", line 41, in get_changeset self.sync() File ""/usr/lib/python2.4/site-packages/trac/versioncontrol/cache.py"", line 107, in sync (str(current_rev), path, kind, action, File ""/usr/lib/python2.4/site-packages/trac/db/util.py"", line 47, in execute return self.cursor.execute(sql_escape_percent(sql), args) File ""/usr/lib/python2.4/site-packages/trac/db/util.py"", line 47, in execute return self.cursor.execute(sql_escape_percent(sql), args) IntegrityError: duplicate key violates unique constraint ""node_change_pk"" }}} Workaround: do a `trac-admin $TRAC_ENV resync`. " defect closed highest 0.10.4 version control 0.10 blocker fixed pysqlite, weird, postgresql brad@…