Ignore reparse points on network file systems. The destination is unl…

[marktucker]

Description of Change(s)

Ignore reparse points on network file systems. The destination is unlikely to be accessible from the remote machine. So for example, machine A points to a network location on machine B (//B/share/path/to/some/directory). But on machine B, the directory "C:/path/to/some" that corresponds to "//B/share/path/to/some" is a reparse point that maps to "D:/another/location". If machine A tries to "simplify" this path using knownledge of the reparse point, it ends up with a path like "D:/another/location/directory", which is totally meaningless on machine A. So in this case we have to just ignore the reparse point and machine A can only access the directory using the full path "//B/shared/path/to/some/directory".

• [ X ] I have verified that all unit tests pass with the proposed changes
• [ X ] I have submitted a signed Contributor License Agreement

[jesschimein]

Filed as internal issue #USD-9260

:heavy_exclamation_mark: Please make sure that a signed CLA has been submitted!

[marktucker]

I have signed a CLA through SideFX.

[jesschimein]

/AzurePipelines run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).