It may make sense to traverse repo.mutable.cslist until revision with hex and rev properties matching those in actual repository is found. Currently in case something like rollback, rebase or strip was done touching at least two revisions that are already in cslist it is completely regenerated which should have bad performance impact. On the opposite side, querying repository a number of times to get revision information also has bad performance impact (though mostly in non-python version of driver if this querying will be done purely in python).
You caught us doing some quick maintenance, temporarily restricting your repository to read-only access.
Issue #64 new