Long messages cause an error

[lincheoll]

Describe the bug

Long messages cause an error.

To Reproduce

Using PostgreSQL as the database, sending a message longer than 255 characters causes an error.

Alternatively, if the most recent message is too long (an error occurs in factsProvider), the issue arises due to the message length. Since it uses the levenshtein function, the error message:

"levenshtein argument exceeds maximum length of 255 characters"

appears when a long message is processed. This happens immediately when sending a long message at once. Applying slicing resolves the issue, but I'm not sure if that's the right approach.

It would be great if someone could fix this.

I'm curious about the best way to handle this, though I haven't tested it on other databases.

Expected behavior

Long texts or past chat history should not cause errors.

Screenshots

Additional context

I don’t think this happened before… I’m not sure. I don’t know where to look.

[alois8]

+1
(I have this in v0.25.6-alpha.1)

[lincheoll]

@alois8
After checking, such an error does not occur in v0.1.9.
However, there seem to be other issues…

[odilitime]

Encountering this is a v0.1.9 copy

[tercel]

modify to below can work well.
levenshtein( left($1, 255), left(content_text, 255) )