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
This code creates a .tmp file and in case of sudden termination this file will not be cleanup and StufioLibrary will stop to work.
With distributed workflows this .tmp file seems to prevent concurrent save operations. It may work as expected: if two users call write simultaneously one of them will got exception and will have to repeat adding new item. That is good, but may be there would be better approach that will not throw errors.
Library synchronization with BitTorrent, or Dropbox or rclone as I do, may be long enough and those .tmp files may not cleanup in time, and sometimes we encounter save item failures. Database file would conflict or do not correspond to actually synced files. So it seem that StudioLibrary is not intended to be used with such synchronization solutions.
What do you think?
The text was updated successfully, but these errors were encountered:
Yep, if for some reason there is .tmp file, it is impossible to save any pose, you only able to remove that .tmp file by hands, and most of users are not aware of that file((
Hi, @krathjen
It is not clear, the problem the algorithm in studiolibrary.utils.write() resolves. Doc string do not state this.
studiolibrary/src/studiolibrary/utils.py
Line 794 in 0281801
What do you think?
The text was updated successfully, but these errors were encountered: