-
Notifications
You must be signed in to change notification settings - Fork 19
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
Don't know how to / Can't assign UID when uploading #13
Comments
For comparison, here's tilesets from the google doc. Notice that the examples above are missing credentials, and have a different field for the file. Where does this come from? Are they actually being handled differently? |
Viewconfs don't require credentials and can't be assigned a uuid (at the moment). Preventing unauthorized file uploads is more important because those are user-visible (e.g. one can click 'add track' and see the list of tracks that are present). Viewconfs are largely invisible. Unless you know the UUID of a particular viewconf, you won't be aware of its existence. We can make the viewconfs method accept uids. The function To see an example of where we store 'uids', take a look at |
I'll take a swing at this. Being able to give the ID when creating a viewconfig would make it a lot easier to describe reproducers. |
This is implemented and tested: https://github.com/hms-dbmi/higlass-server/blob/7e9519d36b1b91d69c5a5e7755bd43cb28a2762f/tilesets/tests.py#L65-L66 |
Sorry if this something simple I'm missing:
The text was updated successfully, but these errors were encountered: