[Bugs] #2149 UNSP: migration.migrate_from_0 fails with file not found error

[Sugar Labs Bugs]

#2149: migration.migrate_from_0 fails with file not found error
------------------------------------------+---------------------------------
    Reporter:  carrott                    |          Owner:  alsroot                    
        Type:  defect                     |         Status:  new                        
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  sugar-datastore            |        Version:  0.88.x                     
    Severity:  Major                      |       Keywords:  migration dextrose r!      
Distribution:  Fedora                     |   Status_field:  Unconfirmed                
------------------------------------------+---------------------------------

Comment(by carrott):

 Regarding which step screws up, as far as I can tell there is only one
 step, that performed in migration_from_0(). This seems surprising since
 the current journal version is version 5. The migration_from_0() doesn't
 seem to properly migrate the journal. The shell.log (attached) is full of
 exceptions.

 Date parsing goes wrong, corrupting the self._cached_row
 {{{
 Traceback (most recent call last):
   File "/usr/lib/python2.6/site-packages/jarabe/journal/listmodel.py",
 line 153, in on_get_value
     ctime = time.mktime(time.strptime(ctime, CTIME_FORMAT))
   File "/usr/lib/python2.6/_strptime.py", line 454, in _strptime_time
     return _strptime(data_string, format)[0]
   File "/usr/lib/python2.6/_strptime.py", line 325, in _strptime
     (data_string, format))
 ValueError: time data dbus.ByteArray('1282443424', variant_level=1) does
 not match format '%Y-%m-%dT%H:%M:%S'
 }}}

 Access to the corrupt self._cached_row then fails
 {{{
 IndexError: list index out of range
 Traceback (most recent call last):
   File "/usr/lib/python2.6/site-packages/jarabe/journal/listmodel.py",
 line 124, in on_get_value
     return self._cached_row[column]
 }}}

 I would suggest making the self._cache_row calculations failure atomic
 and/or more robust to bad data.

 The journal itself shows a strange progress bar with 0% (see attached
 screenshot) which remains even when you re-open an entry.

 If anyone needs example journals, I have about 20 from os767, but they
 have personal photos and stories so I don't think I should post them here.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/2149#comment:4>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system