Not all stop sequences are created equal #534
Closed
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.
This PR fixes some stop sequences not being matched. When generating and decoding tokens, sometimes a single token will generate the stop sequence plus additional characters. This caused
if seq.output_text.endswith(stop_str):
not to behave as expected.For example. If a stop sequence is defined as
",
and the model generates","
as a single token, as is the case withEleutherAI/gpt-neox-20b
, then the stop sequence will not be detected and generation will not stop.This is a small PR that, instead of checking only the end of the generated sequence, checks the entire sequence for the stop sequence