Content locations using Windows UNC paths are inaccessible

[echo6ix]

Just documenting this issue per our discussion on Discord.

I spent an hour or so looking into UNC paths, kind of hit a wall. The first problem was the fact that the library I'm using for globbing (doublestar) doesn't seem to support UNC paths. I tried removing that and writing the logic myself, but for some reason I'm unable to access any of the folders within the share. I can see the share itself and its contents, but none of the folders inside the share. I get an error saying The system cannot find the path specified. even though it's there and I can access it.

Content locations using Windows UNC paths, //servername/folder, are inaccessible to the app.

Windows users will have to map network locations to a drive either using the file explorer or command line method until the issue is resolved .

[WithoutPants]

I've sent a PR for doublestar to support UNC paths. I can put in a PR to update the vendor copy if wanted, or can wait to see if the PR is accepted and update the local copy then.

With the fix, I was able to scan and access videos over network share without any issue.