-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
🏛️ Improve DPO configuration documentation structure #2561
Conversation
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
with self.assertRaisesRegex( | ||
ValueError, | ||
expected_regex=r"Can't find `pad_token_id` in the `processing_class`. " | ||
r"Explicitly set `tokenizer.pad_token` \(e.g. `tokenizer.pad_token = tokenizer.eos_token`\) " | ||
r"before instantiating the trainer.", | ||
): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably an error: we aren't supposed to test this here, but the num_proc (test_dpo_trainer_w_dataset_num_proc
)
expected_regex=r"Can't find `pad_token_id` in the `processing_class`. " | ||
r"Explicitly set `tokenizer.pad_token` \(e.g. `tokenizer.pad_token = tokenizer.eos_token`\) " | ||
r"before instantiating the trainer.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
new error message
CI fails, I think we can ignore, see #2558 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cewl!
It would also be helpful to include instructions for generating the documentation in the contribution guideline
you know, for the community.🙄
…ingface/trl into better-structure-dpo-config
Good point, done in 43089fa |
What does this PR do?
Before
After
Fixes # (issue)
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.