-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Globus Transfer in fails for new datasets and non-privileged users #10200
Comments
pdurbin
added a commit
to GlobalDataverseCommunityConsortium/dataverse
that referenced
this issue
Jan 10, 2024
pdurbin
added a commit
to GlobalDataverseCommunityConsortium/dataverse
that referenced
this issue
Jan 11, 2024
pdurbin
added a commit
to GlobalDataverseCommunityConsortium/dataverse
that referenced
this issue
Jan 11, 2024
pdurbin
added a commit
to GlobalDataverseCommunityConsortium/dataverse
that referenced
this issue
Jan 11, 2024
pdurbin
added a commit
to GlobalDataverseCommunityConsortium/dataverse
that referenced
this issue
Jan 11, 2024
pdurbin
added a commit
to GlobalDataverseCommunityConsortium/dataverse
that referenced
this issue
Jan 11, 2024
pdurbin
added a commit
to GlobalDataverseCommunityConsortium/dataverse
that referenced
this issue
Jan 11, 2024
stevenwinship
pushed a commit
that referenced
this issue
Jan 22, 2024
stevenwinship
pushed a commit
that referenced
this issue
Jan 22, 2024
stevenwinship
pushed a commit
that referenced
this issue
Jan 22, 2024
stevenwinship
pushed a commit
that referenced
this issue
Jan 22, 2024
stevenwinship
pushed a commit
that referenced
this issue
Jan 22, 2024
stevenwinship
pushed a commit
that referenced
this issue
Jan 22, 2024
This was referenced Feb 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps does it take to reproduce the issue? Missed in testing: When transfer to a managed dataset is initiated, the Globus endpoint does not have the subdirectories required to store datafiles for it. A non-privileged user is given permission to write to that (non-existent) directory, but that permission doesn't allow the non-privileged user to create the directory. (Once the dir exists, e.g. from a privileged user (one who has permissions to create the directory independent of Dataverse) performing a transfer, or the dir being created manually, a non-privileged user can make a success transfer of files to Dataverse. These are potential work-arounds until the bug is fixed.)
Which version of Dataverse are you using?
v6.1
PR to follow - adding code to create the nested directories required dynamically
The text was updated successfully, but these errors were encountered: