We’re using Egnyte as our cloud fileserver which allows us to have Mapped Drives. We’re experiencing an issue with Grasshopper .gh files are creating multiple copies of what seems to be temporary backups when two users make changes to the same file.
Does Grasshopper create a temp file in the background for changes and is it supposed to be deleted once the main file is saved with new changes? Any insight into how this might be happening from the application side would be super helpful.
It’s somewhat hard to explain in writing so I’ve attached a video:
After speaking with Egnyte they’re aware of similar issues with other applications but the application handles the deletion of the temporary file. In this case we suspect the temporary file isn’t being deleted by the application and Egnyte is recognizing this file and syncing it back to the drive. Just a guess though.
What this amounts to for us is a ton of duplicate .gh files with weird 10 digit strings on our fileserver.
One more thing that could reproduce this issue which Egnyte brought to my attention was a more common behavior like file browsing. For example, when a user clicks on a file in Windows Explorer, the file ownership could be changed in this context causing the temp files to be created and recognized by Egnyte as file changes.
In this image we’ve labeled for clarity:
Red = Duplicate files
Blue = Conflict copy file generated by Egnyte
Green = Original file
Cheers,
Bob