No feedback during "Indexing repository" phase of environment initialization

[clepple+trac@…]

If possible, it would be nice to have some sort of feedback during the environment initialization phase. For instance, you could have a background thread that occasionally prints the revision that is currently being indexed, then goes back to sleep for a certain amount of time (rather than simply printing every revision as it is encountered, and thus slowing down the indexing operation). Or it could print status after every 100 commits.

[Steve Milner]

This still happens in the 0.9.3. While it isn't a killer it's hard to tell if it is hung or doing something.

[Christian Boos]

This is even more useful now that the resync is committing after each revision sync (more robust, but also much slower).

A few "." printed after every commit or every 10 commits would be adequate, I think.

[Christian Boos]

Well, I couldn't find a clean way to get this information out without modifying the versioncontrol API, so this will have to wait 0.12.

[Christian Boos]

Now that sync() is called explicitly by trac-admin, this can be done easily.

[Christian Boos]

Implemented in r5138 (trunk) and r5139 (0.10-stable).

Note that this changes the signature of the Repository.sync() recently introduced in the VC API (see #5014).

[Matthew Good]

This change is not backwards compatible with existing VC plugins and needs reverted, at least on the 0.10-stable branch. See for example the Trac+Darcs plugin: ​http://progetti.arstecnica.it/trac%2Bdarcs/browser/tracdarcs/repository.py#L217

[Christian Boos]

Well, you can bring the topic on the trac-dev mailing list if you want, but sync() is only officially documented since 0.10.4, so there's no breakage here (see #5014).

If we really want to support the old API, then the change must be completed in order to check for the arity of the sync() method.

[Christian Boos]

Follow-up to comment:8

If we really want to support the old API, then the change must be completed in order to check for the arity of the sync() method.

OK, turns out to be not a big deal, even useful considering that sync() was not documented and that we're now explicitly calling it. I'll do the same for the sync_changeset recently introduced as well.

[Matthew Good]

Replying to cboos:

Well, you can bring the topic on the trac-dev mailing list if you want, but sync() is only officially documented since 0.10.4, so there's no breakage here (see #5014).

Well, despite being undocumented the method was still required. Trac assumed that repository connectors would all use the CachedRepository object which provided this method, which was not really a safe assumption.

If we really want to support the old API, then the change must be completed in order to check for the arity of the sync() method.

Ok. I'd also prefer to rename it to "rev_callback" to make its purpose more clear.

[Christian Boos]

Matt's concerns hopefully addressed in r5144.

I raised a NotImplemented error so that a trac-admin resync <rev> will explicitly fail instead of succeeding with a "<rev> resynced." message that would be erroneous.

For the ultimate Repository.sync API documentation, let's discuss that on #5014…