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
When calling getFile with a destination that is an absolute path (or more generally, with a path including /) the file is incorrectly stored locally.
The cause of the issue is the replacement of / with \\ in getCleanedSmbClientArgs for the destination argument.
I think this can be somewhat avoided by using the workingDir option, but strictly speaking the destination argument should be exempt from that sort of path modification.
The text was updated successfully, but these errors were encountered:
I actually was having the same issue but according to the smbclient manual the get command has the following configuration: get [local file name]. So, the getFile function destination argument is actually the destination name of the file and not the destination location. You can use then the workingDir argument to define where you want to place the file.
When calling
getFile
with a destination that is an absolute path (or more generally, with a path including/
) the file is incorrectly stored locally.The cause of the issue is the replacement of
/
with\\
ingetCleanedSmbClientArgs
for the destination argument.I think this can be somewhat avoided by using the
workingDir
option, but strictly speaking the destination argument should be exempt from that sort of path modification.The text was updated successfully, but these errors were encountered: