collection-monitor shuts down if it fails to read a file

Bug #515264 reported by Chris Wagner
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Resonate
Fix Committed
High
Chris Wagner

Bug Description

This can happen if a file is removed between the time the collection-monitor constructs its list of files (that it needs to scan) and the time that it actually tries to read the tags for a removed file. Here's what the given error looks like:
  collection-monitor shutting down because of error: /path/to/song.mp3: getModificationTime: does not exist (No such file or directory)

The best way to handle this would probably be to do a general handling of any IO errors that occur when trying to read a particular file, simply reporting any errors that occur and moving along over the rest of the collection.

Changed in resonate:
status: New → Confirmed
importance: Undecided → Low
Changed in resonate:
importance: Low → Medium
Changed in resonate:
importance: Medium → High
Changed in resonate:
status: Confirmed → In Progress
Revision history for this message
Chris Wagner (chris-wagner) wrote :

Fixed in revision 831.

Changed in resonate:
assignee: nobody → Chris Wagner (chris-wagner)
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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