different users storing same file to same folder results in 403

Description

User report of an error from Gates Foundation related work. This is preventing Gates data contributors from uploading data files to Synapse.

Two users were trying to store the same file (same contents/md5) to the same directory with the following line of Python code (parent ID and file changed):

The original creator stores the file successfully. Subsequent attempts by a DIFFERENT user fail with a 403, like:

If the subsequent attempts omit the 'name' parameter, it succeeds:

Environment

Any

Activity

Show:
Jordan Kiang
October 30, 2020, 2:26 PM

can you provide the synapser code you are using that is giving the 403 in the case with those meta data templates. Is it just a synStore on any of the files in folder syn18512044 (Metadata Templates) with your nicole.kauer user?

Nicole Kauer
October 30, 2020, 4:14 PM
Edited

, it’s been hard finding the right steps to reproduce because it is magically working now. The code that failed yesterday was using the approach below to update files. I just ran the code again today and it worked. Since yesterday, nothing changed about my environment, the packages used, etc.

Yesterday, the actual code (not the repro above) had this error below, but I do not have the same issue today.

So…maybe it’s magically fixed? Are Halloween miracles a thing?

Jordan Kiang
October 30, 2020, 5:18 PM
Edited

Hmm, that’s odd, I haven’t yet been able to repro it (outside of my mistaken repro as described above). Did you save over the file entity from e.g. the web after getting the 403 in and then were able to successfully save it via synapser? Although that doesn’t repro for me either.

Nicole Kauer
October 30, 2020, 5:31 PM

, I did not. However, I did just notice something could have changed in my environment without me realizing it. The terminal in my Rstudio instance (from SC) has been acting weird. It keeps trying to load the cache and sometimes runs the previous commands. It apparently loaded previous commands to install the synapseclient. It had some weird errors and ultimately failed, but maybe it somehow sorted out the problem. I am probably grasping at straws since this isn’t reproduceable now. I am going to assume something in the environment was acting up. Perhaps we close this and if it rears it’s ugly head in a reproduceable way, we can add a repro and reopen?

Jordan Kiang
October 30, 2020, 5:33 PM

Okay sounds good. 🙈🙉🙊

Fixed

Assignee

Jordan Kiang

Reporter

Kenneth Daily

Labels

Validator

Kara Woo

Development Area

Synapse Core Infrastructure

Release Version History

None

Sprint

None

Fix versions

Affects versions

Priority

Critical
Configure