fixed error message for GatedRepoError

[DawiAlotaibi]

Context

What is the purpose of this PR? Is it to

• add a new feature
• fix a bug
• update tests and/or documentation
• Cleanup

Please link to any issues this PR addresses.
#1831

Changelog

What are the changes made in this PR?
Checked if args.hf_token is passed or not. and printed a message accordingly.

Test plan

None

• run pre-commit hooks and linters (make sure you've first installed via pre-commit install)
• add unit tests for any new functionality
• update docstrings for any new or updated methods or classes
• run unit tests via pytest tests
• run recipe tests via pytest tests -m integration_test
• manually run any new or modified recipes with sufficient proof of correctness
• include relevant commands and any other artifacts in this summary (pastes of loss curves, eval results, etc.)

UX

If your function changed a public API, please add a dummy example of what the user experience will look like when calling it.
Here is a docstring example
and a tutorial example

• I did not change any public API
• I have added an example to docs or docstrings

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchtune/1832

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 550134a with merge base 4107cc4 ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

Hi @DawiAlotaibi!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 67.34%. Comparing base (c70ad29) to head (12bed0a).
Report is 5 commits behind head on main.

Files with missing lines	Patch %	Lines
torchtune/_cli/download.py	66.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1832      +/-   ##
==========================================
+ Coverage   67.30%   67.34%   +0.04%     
==========================================
  Files         304      305       +1     
  Lines       16000    16015      +15     
==========================================
+ Hits        10768    10785      +17     
+ Misses       5232     5230       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[joecummings]

Thanks for this fix @DawiAlotaibi! Two things:

1. Would you mind updating the appropriate test for this change?
2. Can you sign the CLA?

[DawiAlotaibi]

Thanks for this fix @DawiAlotaibi! Two things:

1. Would you mind updating the appropriate test for this change?
2. Can you sign the CLA?

Added the test cases please let me know if they are appropriate. For the CLA I am waiting on confirmation to sign it and it might take some time, will let you know once I have signed it.

[joecummings]

This looks great! Thanks for such a quick fix - will merge when CI is green