Fix jinja error on case-insensitive roles and 0-len messages result#2201
Open
Reithan wants to merge 2 commits into
Open
Fix jinja error on case-insensitive roles and 0-len messages result#2201Reithan wants to merge 2 commits into
Reithan wants to merge 2 commits into
Conversation
Owner
|
Why >1 and not >=1? Prefilling a single turn should be legal too. |
Author
|
If == 1, after you run the prefill, the turn array is empty and Jinja throws an error.
|
Author
|
Possibly there's a better resolution for this, because the variability on what the jinja template you're using may or may not support is pretty big. |
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
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.
Code is not detecting "Assistant" from ST.
When it is fixed, Jinja template errors consistently if there is only 1 assistant message, due to
Jinja formatting failed: list object has no element 0Both fixed