You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Will leave 0 byte files around as there is no cleanup. A client may fail to fix it. Any automated client will now have corrupted files and need to do full hash or size check of all files to fix it.
Could fall on client side depending on viewpoint. If errors out, verify all files. So, can be closed if that is the end viewpoint. Didn't look at ftp specs on it.
The text was updated successfully, but these errors were encountered:
Xavron
changed the title
Rare possibility for corrupted files to be left around
Rare possibility for 0 byte files to be left around
May 7, 2024
Both java.io.File & scoped storage are affected here.
When storing a file, the file is created:
https://github.com/ppareit/swiftp/blob/df0db0eeece48267c27e98da6117fd9d61e05b4f/app/src/main/java/be/ppareit/swiftp/server/CmdAbstractStore.java#L88C1-L103C18
Any issue at all following it such as during openDataSocket() for example:
https://github.com/ppareit/swiftp/blob/df0db0eeece48267c27e98da6117fd9d61e05b4f/app/src/main/java/be/ppareit/swiftp/server/CmdAbstractStore.java#L146C1-L146C51
Will leave 0 byte files around as there is no cleanup. A client may fail to fix it. Any automated client will now have corrupted files and need to do full hash or size check of all files to fix it.
Could fall on client side depending on viewpoint. If errors out, verify all files. So, can be closed if that is the end viewpoint. Didn't look at ftp specs on it.
The text was updated successfully, but these errors were encountered: