Trainer.model.push_to_hub() does not allow a private repository flag

[qzc438]

System Info

As the title described.

Who can help?

No response

Information

• The official example scripts
• My own modified scripts

Tasks

• An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
• My own task or dataset (give details below)

Reproduction

Use the function Trainer.model.push_to_hub().

Expected behavior

Trainer.model.push_to_hub() allows a private repository flag.

[amyeroberts]

Hi @qzc438, thanks for opening this issue!

The easiest way to enable this is to set hub_private_repo=True in TrainingArgs.

I would be nice to have this as a flag in the method too. Would you like to open a PR to add this? cc @muellerzr

[qzc438]

Dear team,

Can you check this link: #25219
From what I can see, hub_private_repo=True is not working.

Sincerely,
Zhangcheng Qiang

[amyeroberts]

Hi @qzc438,

Could you run the example code from this comment and confirm if it works?

I was unable to reproduce the reported issue in #25219. If you can provide an minimal code snippet which reproduces hub_private_repo=True not working and your environment information then we can try and dig into it

[qzc438]

Dear team, I am trying to, but I cannot find a way to track the visibility of the hugging face models in the audit log. I have tried your enterprise version, but this information is still untrackable. Sincerely, Zhangcheng Qiang

…

On Tue, 27 Aug 2024 at 20:49, amyeroberts ***@***.***> wrote: Hi @qzc438 <https://github.com/qzc438>, Could you run the example code from this comment <#25219 (comment)> and confirm if it works? I was unable to reproduce the reported issue in #25219 <#25219>. If you can provide an minimal code snippet which reproduces hub_private_repo=True not working and your environment information then we can try and dig into it — Reply to this email directly, view it on GitHub <#32909 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOVDZBHVTA3CQ5WSB25XF7TZTRKT3AVCNFSM6AAAAABM3IYLBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJSGE4DONRZGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[amyeroberts]

Hi @qzc438, are you referring to these? Is this related to this issue?

[qzc438]

Yes, I am not sure whether the audit log provides the function to check visibility.

[amyeroberts]

By visibility, do you mean whether the created repo is public or private?

[qzc438]

Yes, you are right.

[amyeroberts]

I'm not super familiar with the audit logs - however I think they're centered around recording actions and activity of users.

For a given repo and its name, you should be able to see directly on the hub whether it's private e.g. for a repo of mine

[qzc438]

Yes, I see. The main point is that once you set the repository to private or public during creation, any changes in the code will not reflect the visibility. I tried to use the audit log to check if any intermediate changes happened.

[amyeroberts]

once you set the repository to private or public during creation, any changes in the code will not reflect the visibility

@qzc438 Just to be clear and make sure I understand the behaviour you're describing are you saying that:

• A repo is created- let's say with the name foo/bar and public visibility
• You run a training pass, with push_to_hub_model_id="foo/bar" and hub_private_repo=True set in the training arguments
• When trainer.push_to_hub is called, the artefacts are pushed to foo/bar, and the repo foo/bar remains public

Is this correct?