Skip to content

Conversation

@garrett361
Copy link
Owner

Squashes various commits and rebases on top of latest upstream main.

@fabianlim
Copy link
Collaborator

fabianlim commented Jun 24, 2025

@garrett361 i didnt realize there is a quality check, its failing the check now. otherwise looks quite good to me

"{% endif %}"
"{% endfor %}"
),
"granite": (
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure if this is meaningful, since there are going to be many iterations on these templates. I feel its better to allow the template to be a file path, and it gets read in

Copy link
Owner Author

@garrett361 garrett361 Jun 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Divya required this for her work. Easy to drop this later since it's a standalone commit.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could we have a feature that we can set chat_template_name to reference a file, and that it could be read and set here. two options;

  1. set chat_template_name="custom" and have a few flag chat_template_custom_file to point to the new file
  2. overload chat_template_name to simply point to a new file.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think I'll do 2: if chat_template_name isn't in CHAT_TEMPLATES, then try to read in the text from a file at path chat_template_name. Kinda hacky, but then we don't have to add more flags.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm.. but maybe 1. is better because its more consistent..

@garrett361
Copy link
Owner Author

@fabianlim also didn't realize about the check; guess it's only activated when PR-ing against main.

@garrett361 garrett361 force-pushed the padding-free-squashing branch 2 times, most recently from eed9785 to 76dde18 Compare June 25, 2025 14:33
@garrett361
Copy link
Owner Author

Fixed the CI lint failures.

@garrett361 garrett361 force-pushed the padding-free-squashing branch from 76dde18 to 2b1cfaf Compare June 25, 2025 14:55
@fabianlim
Copy link
Collaborator

I think this will be a good to merge soon, although we need to document down what is missing in comparison to padding-free branch

  1. accept a train_file input
  2. parquet file support and additional model args Small Updates to Padding Free Branch #2
  3. tools and documents (is this still needed)? Add Support For Tools and Documents Chat Template #3
  4. dataloader tester Script for Data Loading Testing #7
  5. add_column is slow so use pandas to load dataset https://github.com/garrett361/open-instruct/pull/6/files

@garrett361 garrett361 force-pushed the padding-free-squashing branch from 71ef31f to b2fe4b9 Compare June 27, 2025 17:41
@garrett361 garrett361 force-pushed the padding-free-squashing branch from b2fe4b9 to 1ca40dc Compare June 27, 2025 19:07
@fabianlim
Copy link
Collaborator

this seems to be superceeded by the series of PRs #17 , etc.. so maybe we should close it?

@garrett361
Copy link
Owner Author

Closing, due to superceeding PRs.

@garrett361 garrett361 closed this Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants