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
The self-hosted GitHub runners would need the restricted models and datasets to already be cached, as there is no means to authenticate with Hugging Face or corresponding platforms due to the absence of user interaction in GitHub Actions. For example, LLAMA2 70B.
Potential fix:
Login to Hugging Face through Hugging Face cli when setting the system for self-hosted GitHub runner. This would store the token to cache and use every time when restricted models are downloaded.
Edit:
Hugging Face document for command line interface can be found here
The text was updated successfully, but these errors were encountered:
The self-hosted GitHub runners would need the restricted models and datasets to already be cached, as there is no means to authenticate with Hugging Face or corresponding platforms due to the absence of user interaction in GitHub Actions. For example, LLAMA2 70B.
Potential fix:
Login to Hugging Face through Hugging Face cli when setting the system for self-hosted GitHub runner. This would store the token to cache and use every time when restricted models are downloaded.
Edit:
Hugging Face document for command line interface can be found here
The text was updated successfully, but these errors were encountered: