Commit 87798bd
authored
fix: AdvcancedSQLiteSession conversation branching from turn number
- So far if e.g. from_turn_number=3 is passed, only turns 1 and 2 are copied, not 3
- This is unintuitive because the function is called branch_from_turn()
- In conjunction with _validate_turn() it is also limiting functionality in that it doesn't allow branching from the latest turn (_validate_turn() raises an error if from_turn_number=n+1 is passed in an n-turn conversation, so users would have to hack their way around it by adding a dummy message as n+1st turn in order to copy the first n turns)
- In case we're preventing branching from the latest turn on purpose for some reason please let me know - if so, what would be the preferred way to fork a conversation from the latest message? (My use case is that I want to produce multiple alternative messages from the same conversation history)1 parent 73e7843 commit 87798bd
1 file changed
+1
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
815 | 815 | | |
816 | 816 | | |
817 | 817 | | |
818 | | - | |
| 818 | + | |
819 | 819 | | |
820 | 820 | | |
821 | 821 | | |
| |||
0 commit comments