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
Problem: When I try to submit a job using onedatashare.org where the destination I want all of the files to end up in a certain path, the resulting path supplied is the absolute path starting from the users home directory and not the absolute path.
To Re-create:
Add 2 servers(2nd one being an sftp/scp/ftp server).
Try submitting a job writing to the 2nd server, and in this view select a directory to dump the LHS files into.
Say you are writing some collection of files from the LHS to the RHS into a directory called output/
The frontend submits the TransferJobRequest such that the destination path in the request is /output. Which is incorrect bc there is no folder called output in the root but there is a folder /home/cc/output. Essentially the frontend is never aware of the users home directory and this is a bad assumption to make.
If you notice that after select an endpoint to list the sftp://, ftp:// at the top of the endpoint file list is the actual path being used which is not correct. I believe that this path is getting used as the destination path thus fixing the file view path to be correct will result in the transfer requests working correctly.
The text was updated successfully, but these errors were encountered:
Problem: When I try to submit a job using onedatashare.org where the destination I want all of the files to end up in a certain path, the resulting path supplied is the absolute path starting from the users home directory and not the absolute path.
To Re-create:
Say you are writing some collection of files from the LHS to the RHS into a directory called
output/
The frontend submits the TransferJobRequest such that the destination path in the request is
/output
. Which is incorrect bc there is no folder calledoutput
in the root but there is a folder/home/cc/output
. Essentially the frontend is never aware of the users home directory and this is a bad assumption to make.If you notice that after select an endpoint to list the
sftp://, ftp://
at the top of the endpoint file list is the actual path being used which is not correct. I believe that this path is getting used as the destination path thus fixing the file view path to be correct will result in the transfer requests working correctly.The text was updated successfully, but these errors were encountered: