You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this case, I can no longer split by newlines, as if I do so, I will end up with broken up sentences:
Hello, this is a test of verbose JSON. This message is
meant to be really long so it can line break, but it won't.
Thank you.
and if I try to read the text of the segments instead, I will simply lose the newlines altogether: Hello, this message is long enough to have a line break, so it will have a line break. Thank you.
I would prefer if the full text in verbose_json did not have the inserted newlines, and maybe on top of that, if the segments had a marker if they're a full line or if text follows after them, so the text can be available both in the full text and reconstructed correctly from the segmented texts.
Regular JSON:
verbose_json:
actual full output:
This becomes a problem when one is trying to sort out actual newlines for filtering out hallucinations:
In this case, I can no longer split by newlines, as if I do so, I will end up with broken up sentences:
and if I try to read the text of the segments instead, I will simply lose the newlines altogether:
Hello, this message is long enough to have a line break, so it will have a line break. Thank you.
I would prefer if the full
text
inverbose_json
did not have the inserted newlines, and maybe on top of that, if the segments had a marker if they're a full line or if text follows after them, so the text can be available both in the fulltext
and reconstructed correctly from the segmentedtext
s.Relevant code to test these as follows:
The text was updated successfully, but these errors were encountered: