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 is probably a wont fix for now as it will require a significant development effort.
Walking the directory structure that uses symlinks will not work the existing golang filepath.Walk function does not follow symlinks. To support this will need a redesign of existing behavior and replacing the filepath.Walk function with a bespoke implementation that is able to follow nested directory symlinks without breaking regexp expression matching.
Example of what I'm talking about..
lets say you have a regexp that wants to look for filepaths hat end in "log" but start with "/var/log/" that's a valid regexp.
But lets now say that you have "/var/log/" as a symlink to something like "/var/tmp/logs" the regexp described above will no longer match because once you evaluate the symlinks to get the real path on disk... the regexp logic will be using that real path not the symlink.
This gets complicated further once you have nested directory symlinks.
Presently symlinks don't work for --log-path args, but it would be 💯 if they did
The text was updated successfully, but these errors were encountered: