Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add backwards compatibility for old DatasetID's #75

Closed
kmdouglass opened this issue Feb 6, 2017 · 1 comment
Closed

Add backwards compatibility for old DatasetID's #75

kmdouglass opened this issue Feb 6, 2017 · 1 comment

Comments

@kmdouglass
Copy link
Owner

Here's what happens when you try to open an old Datastore (1.0.1 and below) with the current 1.1.1:

myDB = db.HDFDatastore(Path('./datastore.h5'))
Unexpected error when loading the Datastore's persistent state: <class 'TypeError'>

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-4-e26258ed339c> in <module>()
      1 # Specify the database
----> 2 myDB = db.HDFDatastore(Path('./datastore.h5'))

/home/douglass/src/bstore/bstore/database.py in __init__(self, dsName, widefieldPixelSize)
    259 
    260         # Read the persistence data from the HDF file
--> 261         self._loads()
    262 
    263         # Lock file to prevent concurrent writes

/home/douglass/src/bstore/bstore/database.py in _loads(self)
    728             with h5py.File(str(self._dsName), mode='r') as file:
    729                 serialObject = file[self._persistenceKey]
--> 730                 objFromHDF = pickle.loads(serialObject.value)
    731                 self.__dict__.update(objFromHDF.__dict__)
    732         except OSError:

TypeError: __new__() missing 1 required positional argument: 'replicateID'
@kmdouglass kmdouglass added this to the v1.2.0 milestone May 10, 2017
@kmdouglass kmdouglass added this to TODO in version 1.2.0 May 10, 2017
@kmdouglass kmdouglass removed this from the v1.2.0 milestone Dec 14, 2017
@kmdouglass
Copy link
Owner Author

It's likely that no one will ever use 1.0.1, so I'm closing this with a Won't Fix label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

1 participant