#4454 HIGH Update.: Activity will not close if the write_file method raises an exception

[Zarro Boogs per Child]

#4454: Activity will not close if the write_file method raises an exception
---------------------+------------------------------------------------------
  Reporter:  pascal  |       Owner:  tomeu   
      Type:  defect  |      Status:  reopened
  Priority:  high    |   Milestone:  Update.1
 Component:  sugar   |     Version:          
Resolution:          |    Keywords:          
  Verified:  0       |  
---------------------+------------------------------------------------------

Comment(by Eben):

 Yes, I agree that the option to cancel the "stop" is important.  I think
 we should have [Cancel] [Stop anyway] buttons.

 I also think that the message can be more meaningful than "all current
 work will be lost."  On a system with incremental auto-saves, there's no
 way to know what exactly will be lost.  We should keep a timestamp around
 (or just query the Journal, once we have versions) and offer: "Keep Error:
 Changes made in the past <n> minutes will be lost."  Of course, for
 activities for which incremental saves don't make sense, and for instances
 where no incremental saves have been made since the activity
 started/resumed, we should just say "Keep Error: All changes will be
 lost."

 If we can obtain any more info about why the save failed, let me know so I
 can consider how to convey that info.

-- 
Ticket URL: <http://dev.laptop.org/ticket/4454#comment:12>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system