[Frontend] Support optional auto truncation #3721
Open
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.
Motivation
#2876 enforces a strict check that disallows cases where the sum of the number of input tokens and
max_new_tokens
exceeds the context length. However, as @merrymercy pointed out and several reports ([1] [2]) indicate, this check may be too restrictive for users who want to set a very large fixedmax_new_tokens
value when the input length is not easy to determine or not important.Modifications
This PR introduces an optional auto-truncation feature by integrating the existing
allow_auto_truncate
option fromserver_args
intoTokenizerManager
.Checklist