[Bug]: Regenerated responses will hide all other messages on a (seemingly) random basis

[ThomasBaruzier]

What happened?

I've seen this bug around 10% of the time when regenrating responses. When it happens, upon the end of generation of a regenerated response, all above messages vanish. A reload of the web page fixes this bug.

Steps to Reproduce

I haven't found a way to reproduce the bug determiniscally, but it happens with any endpoint :/

1. Write a few messages
2. Regenerate some of them
3. Hope that bad luck is with you in order to get the bug

What browsers are you seeing the problem on?

No response

Relevant log output

No response

Screenshots

screen.webm

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Thanks for noticing this, I've noticed it myself time to time, about 10% like you said (usually when I'm being aggressive with regenerations). Hope to triage/resolve by the next release

[xyqyear]

This is very easy to reproduce:

Just keep regenerating until the total number of messages in this conversation exceeds 16 in total in all branches, then refresh the page.

see my reply in #4761

Update: Nevermind. It only breaks in the forked conversation. Following the above steps in a new conversation won't have any issues.

[danny-avila]

I believe this issue was fully realized and addressed in this recent PR: #5833

The fix addresses an edge case for regeneration/re-submission of edited message that could be the root cause here.

The only other edge case we've identified is when messages are not ordered in created order, which messes up the branching, and that was addressed here: #4761