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
Right now they are backed by byte slices. This leads to some incorrect
behavior on Windows. CASInitialContentsFetcher will create symlinks
containing forward slashes, which we then hand over to WinFSP without
any translation in between.
This change modifies symlinks to be backed by a path.Parser. This means
that at any point where we need to convert a symlink to a string
representation, we need to perform an explicit conversion to the
expected path format.
What is a bit annoying is that the st_size of symlinks on UNIX needs to
match the amount of data returned by readlink(). This means that symlink
objects can no longer be aware of their own size. We therefore remove
the SizeBytes attribute from these files. The FUSE and NFSv4 backends
will now consider both AttributesMaskSizeBytes and
AttributesMaskSymlinkTarget to determine the file's real size.
Fixes: #213
0 commit comments