This repository was archived by the owner on Apr 23, 2026. It is now read-only.
Revert "chore: bump the training library to 0.8.0 and refactor tokenizer usage"#3269
Closed
courtneypacheco wants to merge 1 commit intomainfrom
Closed
Revert "chore: bump the training library to 0.8.0 and refactor tokenizer usage"#3269courtneypacheco wants to merge 1 commit intomainfrom
courtneypacheco wants to merge 1 commit intomainfrom
Conversation
mergify
Bot
added
ci-failure
…zer usage" Signed-off-by: Courtney Pacheco <[email protected]>
courtneypacheco
force-pushed
the
revert-3250-update-training
branch
from
b046aa9 to
e176c42
Compare
mergify
Bot
added
ci-failure
Contributor
|
@courtneypacheco i dont think this is needed anymore |
Contributor
Author
|
Closing! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts #3250 because it was merged after #3254, which was reverted because the unit tests stopped running after that PR. There might not be anything wrong with this PR, but we need to re-validate this PR by forcing it to undergo unit + functional testing.