fix: 🐛 pass token when retrieving the split names
COLLABORATOR
Currently, it does not work with https://huggingface.co/datasets/mozilla-foundation/common_voice_7_0/blob/main/common_voice_7_0.py#L146 (which was the goal), because `dl_manager.download_config.use_auth_token` is ignored, and the authentication is required to be use `huggingface-cli login`.
In my use case (dataset viewer), I'd prefer to use a specific "User Token Access", with only the "read" role (https://huggingface.co/settings/token).

See https://github.com/huggingface/datasets-preview-backend/issues/74#issuecomment-1007316853 for the context
2022-01-07T10:46:59Z
https://github.com/huggingface/datasets/pull/3545#issuecomment-1007311968
https://api.github.com/repos/huggingface/datasets/issues/3545
IC_kwDODunzps48Clxg
https://api.github.com/repos/huggingface/datasets/issues/comments/1007311968/reactions
2022-01-07T10:57:03Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1007311968
https://avatars.githubusercontent.com/u/1676121?v=4
https://api.github.com/users/severo/events{/privacy}
https://api.github.com/users/severo/followers
https://api.github.com/users/severo/following{/other_user}
https://api.github.com/users/severo/gists{/gist_id}
https://github.com/severo
severo
MDQ6VXNlcjE2NzYxMjE=
https://api.github.com/users/severo/orgs
https://api.github.com/users/severo/received_events
https://api.github.com/users/severo/repos
https://api.github.com/users/severo/starred{/owner}{/repo}
https://api.github.com/users/severo/subscriptions
User
https://api.github.com/users/severo
public
COLLABORATOR
> Simply passing download_config is ok :)

hmm, I prefer only passing use_auth_token. But the question is more: is it correct, in the (convoluted) case if `download_config.use_auth_token` exists and is different from `use_auth_token`? Which one should be used?
2022-01-07T14:40:35Z
https://github.com/huggingface/datasets/pull/3545#issuecomment-1007458570
https://api.github.com/repos/huggingface/datasets/issues/3545
IC_kwDODunzps48DJkK
https://api.github.com/repos/huggingface/datasets/issues/comments/1007458570/reactions
2022-01-07T14:40:46Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1007458570
https://avatars.githubusercontent.com/u/1676121?v=4
https://api.github.com/users/severo/events{/privacy}
https://api.github.com/users/severo/followers
https://api.github.com/users/severo/following{/other_user}
https://api.github.com/users/severo/gists{/gist_id}
https://github.com/severo
severo
MDQ6VXNlcjE2NzYxMjE=
https://api.github.com/users/severo/orgs
https://api.github.com/users/severo/received_events
https://api.github.com/users/severo/repos
https://api.github.com/users/severo/starred{/owner}{/repo}
https://api.github.com/users/severo/subscriptions
User
https://api.github.com/users/severo
public
MEMBER
If both are passed, `use_auth_token` should have the priority (more specific parameters have the higher priority)
2022-01-07T17:38:23Z
https://github.com/huggingface/datasets/pull/3545#issuecomment-1007599227
https://api.github.com/repos/huggingface/datasets/issues/3545
IC_kwDODunzps48Dr57
https://api.github.com/repos/huggingface/datasets/issues/comments/1007599227/reactions
2022-01-07T17:38:23Z
https://api.github.com/repos/huggingface/datasets/issues/comments/1007599227
https://avatars.githubusercontent.com/u/42851186?v=4
https://api.github.com/users/lhoestq/events{/privacy}
https://api.github.com/users/lhoestq/followers
https://api.github.com/users/lhoestq/following{/other_user}
https://api.github.com/users/lhoestq/gists{/gist_id}
https://github.com/lhoestq
lhoestq
MDQ6VXNlcjQyODUxMTg2
https://api.github.com/users/lhoestq/orgs
https://api.github.com/users/lhoestq/received_events
https://api.github.com/users/lhoestq/repos
https://api.github.com/users/lhoestq/starred{/owner}{/repo}
https://api.github.com/users/lhoestq/subscriptions
User
https://api.github.com/users/lhoestq
public