Its possible for an uncompressed file to be stuck in a cyan state if you start scanning and the file becomes unavailable before hashing can complete. This results in a situation where "Find Fixes" will not be sufficient to perform a fix.
Steps to reproduce:
Setup your RomRoot to target a mapped network drive
Place a large uncompressed file somewhere in your RomRoot, approximately 2gb or larger to ensure you have enough time for the next steps
Scan the RomRoot
While the file is scanning, quickly disconnect the network drive
Notice the file appears in the RomVault UI but it only has a size and no hashes
Reconnect the network drive
Attempt to fix as normal by doing "find fixes" then "fix roms"
Notice the fix will not work
Expected behavior:
(screenshot)
johnsanc
2 years ago
Its possible for an uncompressed file to be stuck in a cyan state if you start scanning and the file becomes unavailable before hashing can complete. This results in a situation where "Find Fixes" will not be sufficient to perform a fix.
Steps to reproduce:
Setup your RomRoot to target a mapped network drive
Place a large uncompressed file somewhere in your RomRoot, approximately 2gb or larger to ensure you have enough time for the next steps
Scan the RomRoot
While the file is scanning, quickly disconnect the network drive
Notice the file appears in the RomVault UI but it only has a size and no hashes
Reconnect the network drive
Attempt to fix as normal by doing "find fixes" then "fix roms"
Notice the fix will not work
Expected behavior:
The error message should prompt the user to rescan since a file with no hashes at all is not a supported scenario.
(screenshot)