Cannot operate on a closed database

[Emmanuel Blot]

There is a small issue with trac-admin when upgrade is followed by a resync command.

This is a very minor issue as exiting/restarting the administration console bypasses the issue.

python2.4 trac/admin/console.py /local/db/trac/project
Welcome to trac-admin 0.11dev-r208
Interactive Trac administration console.
Copyright (c) 2003-2007 Edgewall Software

Type:  '?' or 'help' for help on commands.

Trac [/local/db/trac/project]> upgrade
Upgrade done.
Trac [/local/db/trac/project]> resync
Resyncing repository history...
Command failed: Cannot operate on a closed database.
Trac [/local/db/trac/project]> quit

r208 here matches [5148].

[Christian Boos]

Ok, noted.

Btw, 0.11dev-r208, does that mean you're a happy SVK user? ;-)

[Emmanuel Blot]

Replying to cboos:

Btw, 0.11dev-r208, does that mean you're a happy SVK user? ;-)

Not at all, I've never used SVK.

However as our Trac is a bit "customized" (the kind of customization that is hard to achieve with plugins) I maintain a SVN repository for our Trac, and the official Trac repos is mirrored in a local vendor branch with the help of svn:externals. I sync our repos with Trac's about once a week (which means that we use the latest Trac 0.11dev for real in a 9 people C++ dev team).

[Christian Boos]

Back to the issue… it's strange, I couldn't reproduce this, nor do I see an obvious "close" on the db. What backend are you using? Is this 100% reproducible for you?

[Emmanuel Blot]

Replying to cboos:

Back to the issue… it's strange, I couldn't reproduce this, nor do I see an obvious "close" on the db. What backend are you using? Is this 100% reproducible for you?

The config is SQLite 3, FSFS, Subversion 1.4.2, Python 2.4, Linux/Debian. The repositories have "real" 1.4.2 repository (I mean that I've dump&recreated them when I've upgraded to SVN 1.4.x, in order to take advantage of the embedded changeset compression of the 1.4 series).

There are about 2500 changesets in the repository, and the 'resync' took quite a while (about 15 minutes), while the 'upgrade' took about 1 minute.

Fully reproducible I can't tell, as I had only one repository to sync.

[Christian Boos]

Well, looks like nobody else ever had that issue, closing.