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
{{ message }}
This repository was archived by the owner on Jul 15, 2021. It is now read-only.
currently, we give the user access to S3 so that they can upload assembly/stimulus_set directly themselves.
This potentially generates files that are later unused and unnecessarily exposes data storage.
Would it be worth to have a solution where the user side only mocks the upload and then the real upload happens upon merge?
The downside of this is that the user needs to put the raw files used for packaging somewhere we can access them so we might be back to the same problem..
currently, we give the user access to S3 so that they can upload assembly/stimulus_set directly themselves.
This potentially generates files that are later unused and unnecessarily exposes data storage.
Would it be worth to have a solution where the user side only mocks the upload and then the real upload happens upon merge?
The downside of this is that the user needs to put the raw files used for packaging somewhere we can access them so we might be back to the same problem..
(copied from brain-score/brainio_contrib#37)
The text was updated successfully, but these errors were encountered: