It appears that there is a race condition that can occur when the fix for a set requires a case sensitive rename of the archive and the removal of a file from that archive. RomVault behaves as if it cannot find a reference to the archive it just renamed on the filesystem. Since the removal action happens immediately after the rename, its likely the filesystem was not yet updated with the new name at the time the removal was attempted.
(screenshot)
johnsanc
2 years ago
It appears that there is a race condition that can occur when the fix for a set requires a case sensitive rename of the archive and the removal of a file from that archive. RomVault behaves as if it cannot find a reference to the archive it just renamed on the filesystem. Since the removal action happens immediately after the rename, its likely the filesystem was not yet updated with the new name at the time the removal was attempted.
(screenshot)