Token indices sequence length is longer than the specified maximum sequence length for this model #1833
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.
As of now the tokenizers output a specific warning when an encoded sequence is longer than the maximum specified sequence length, which is model-specific:
It is currently in the
convert_tokens_to_idsand this leads to two issues:encodeorencode_plusmethods with amax_lengthspecified will still output that warning as theconvert_tokens_to_idsmethod is used before the truncation is done. (cf token indices sequence length is longer than the specified maximum sequence length #1791)prepare_for_modelwas introduced, I personally feel that all modifications related to the model should happen in that method and not intokenizeorconvert_tokens_to_ids.This PR aims to slightly change the behavior so that both aforementioned issues may be solved by putting the warning in the
prepare_for_modelmethod if nomax_lengthis specified.