feat: support stop_token_ids parameter. #1097
Merged
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.
When the eos_token_ids is also special tokens it will be skip by default and generation won't stop correctly, so I think vLLM should support
stop_token_ids
like FastChat does. But unlike FastChat,stop_str
should have higher priotity thanstop_token_ids
because right now I only found this case, in other cases,stop_str
works well.Also check #792
Or else there are better solutions?