We are starting to use our new file system tester, and immediately found and fixed two important bugs:
- When too many changes happen in a file system tree, the synchronization stopped:
This was a subtle problem in handling a buffer overflow in the FileSystemWatcher. Now, when too many changes are happening, the internal file system tree is flushed and rescanned for the next synchronization. Not the best solution, but a safe one. An alternative would be to run a high-priority thread that retrieves all the changes in time. But even then, it can not be guaranteed that this error won’t happen anymore. So I think it is better to handle it anyways. - Files could not be write-accessed or deleted while they were transferred:
I knew of this problem, but never observed it in one of the test cases, but our new file system tester catched this one easily. From now on, files are uploaded in “stealth” mode.