Respect BPE cache_capacity when reading JSON - #2420
Open
LysandreJik wants to merge 1 commit into
Open
LysandreJik wants to merge 1 commit into
LysandreJik wants to merge 1 commit into
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
tk-serializecurrently ignores thecache_capacityfield when reading a BPE model fromtokenizer.json.This means that setting
cache_capacity: 0doesn't work as it's replaced by the default BPE cache capacity of 65,536.This fix reads
cache_capacityfrom the BPE JSON configuration when present.PS: not an expert in the codebase so there is very likely a more elegant solution 馃槆 I can confirm that with this I manage to set the cache correctly, though.