Skip to content
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

update docs for tokenizer_legacy #401

Merged
merged 2 commits into from
Aug 15, 2023
Merged

update docs for tokenizer_legacy #401

merged 2 commits into from
Aug 15, 2023

Conversation

winglian
Copy link
Collaborator

No description provided.

@NanoCode012
Copy link
Collaborator

We should clarify the default is True?

@winglian winglian requested a review from NanoCode012 August 15, 2023 11:38
@NanoCode012 NanoCode012 merged commit 47961fd into main Aug 15, 2023
@winglian winglian deleted the doc-tokenizer_legacy branch August 29, 2023 12:58
mkeoliya pushed a commit to mkeoliya/axolotl that referenced this pull request Dec 15, 2023
* update docs for tokenizer_legacy

* add default info
@tongyx361
Copy link

We should clarify the default is True?

May I ask why you default tokenizer_legacy as True?

@NanoCode012
Copy link
Collaborator

@tongyx361 , hey! This was from a year ago. If I recall correctly, it was that the new behavior was not correct/created some issues esp for llama. It's very likely they fixed it and this should be reverted. If you would like, please create a new Issue on this, so we can track this better.

djsaunde pushed a commit that referenced this pull request Dec 17, 2024
* update docs for tokenizer_legacy

* add default info
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