Closed in03 closed 2 years ago
False alarm. Turned out to be a 'sticky-file' that the file server had locked, but still allowed Windows to delete. Although it exists, it's corrupt and fails the linking process. Still reworked the handlers a bit so that failed links are given a proxy: "None"
status and won't be caught by the Offline handler.
Fixed now in #124
Recently pushed changes to check for existing and unlinked for 'Offline' proxies as well, just in case they became online after Resolve was started. Unforunately this was an oversight. Now the existing-unlinked handler attempts to link offline proxies with their
expected_proxy_path
but fails, since the paths don't exist.It would be nice to keep the handlers separate, but they may need to go hand-in-hand. Probably the expected proxy path should be invalidated before both handlers run.