ZODB Browser

POSKeyError while viewing the history of a large'ish OOBTree

Bug #953480 reported by Marius Gedminas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ZODB Browser
Fix Released
High
Unassigned

Bug Description

I've this OOBTree with 55 items and 168 revisions. ZODBBrowser shows the first 12 revisions just fine, and then starts complaining 'Could not load historical state: POSKeyError: 0x2f' for most of the rest, including the latest state.

The time-limited-connection branch of ZODBBrowser can show this history just fine. Perhaps finishing that branch to completion and merging it would be the best way to close this bug?

Revision history for this message
Marius Gedminas (mgedmin) wrote :

I've hunted it down and fixed it in trunk. Expect a 0.10.2 release soon.

This bug was introduced in 0.10.0 with the implementation of the feature requested in bug 497780.

Changed in zodbbrowser:
status: New → In Progress
importance: Undecided → High
Marius Gedminas (mgedmin)
Changed in zodbbrowser:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.