-
Notifications
You must be signed in to change notification settings - Fork 82
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
remove "gated datasets unlock" logic #189
Conversation
also: add two tests to ensure the gated datasets can be accessed
I changed (https://huggingface.co/datasets/severo/dummy_gated/commit/99194748bed3625a941aaf785740df02ca5762c9) severo/dummy_gated to a simpler dataset, without a python script, to avoid having non-related errors. Also in the commit: load the HF_TOKEN from a secret in https://github.com/huggingface/datasets-preview-backend/settings/secrets/actions to be able to run the unit tests
@SBrandeis I added you as a reviewer because it's part of the migration to the new tokens. I use it only to "unlock" the gated datasets (and later on, authenticate so that the server knows the dataset is unlocked). We don't access private datasets for now, so not related to public/private for now. |
By the way: what is the relationship between the token you gave me for dataset-preview-backend, and the gated datasets? Is the gated dataset unlocked for the token? for the user or org related to the token? |
unit tests should be failing due to #188 |
it's a dependency of lm-dataformat, and last version still depends on a vulnerable ujson version
the new "app" tokens on moonlanding can read the gated datasets without having to accept the conditions first, as it occurs for users. BREAKING CHANGE: 🧨 HF_TOKEN must be an app token
Tests are failing tho |
yes, due to #188. See https://huggingface.slack.com/archives/C034N0A7H09/p1648817245991569 |
the new tokens are not related to a user and have read access to the gated datasets (right, @SBrandeis?).
also: add two tests to ensure the gated datasets can be accessed