Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#28 deal with corrupted files properly

open
nobody
None
5
2012-12-07
2006-07-31
Martijn Buijs
No

When a corrupted file is encountered the programs shows
the exception error warning dialog (see error message
below), and continues the other tasks when the error
window is closed. This happens for EVERY file that is
corrupted, so if you have 99 files, you have to close
the window 99 times. I suggest these errors should be
logged, and displayed once when the task is completed.
These errors should be dealt with because creating
backups of bad hard disks is not uncommon.

------------------------------------------------------

java.io.FileNotFoundException:
L:\Textures\crate\crate12.jpg (File is damaged or
corrupted)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(Unknown Source)
at java.io.FileOutputStream.<init>(Unknown Source)
at
net.sourceforge.fullsync.fs.connection.LocalConnection.writeFile(LocalConnection.java:110)
at
net.sourceforge.fullsync.fs.connection.AbstractFile.getOutputStream(AbstractFile.java:157)
at
net.sourceforge.fullsync.impl.FileCopyEntryDescriptor.getOutputStream(FileCopyEntryDescriptor.java:48)
at
net.sourceforge.fullsync.buffer.BlockBuffer.flush(BlockBuffer.java:92)
at
net.sourceforge.fullsync.impl.FillBufferTaskExecutor.flush(FillBufferTaskExecutor.java:140)
at
net.sourceforge.fullsync.Synchronizer.performActions(Synchronizer.java:110)
at
net.sourceforge.fullsync.ui.TaskDecisionPage$4.run(TaskDecisionPage.java:212)
at java.lang.Thread.run(Unknown Source)

Discussion