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
{{ message }}
Repository navigation
Commit 1882130
Browse filesBrowse the repository at this point in the historyBrowse files
fix: use parentID instead of ID ordering for loop exit condition
The loop exit condition compared user.id < assistant.id which breaks
when client/server clocks diverge. Web UI generates message IDs
client-side while server generates assistant IDs, causing clock skew
that makes user IDs sort after assistant IDs. This triggers an infinite
loop generating duplicate assistant messages.
Fix checks assistant.parentID === user.id instead, which correctly
identifies whether the assistant message is responding to the current
user message regardless of ID ordering.
Fixesanomalyco#21335
Co-authored-by: Qwen-Coder <[email protected]>
0 commit comments