fix(session): use parentID instead of message ID ordering in prompt loop#17010
Open
ShenAC-SAC wants to merge 1 commit intoanomalyco:devfrom
Open
fix(session): use parentID instead of message ID ordering in prompt loop#17010ShenAC-SAC wants to merge 1 commit intoanomalyco:devfrom
ShenAC-SAC wants to merge 1 commit intoanomalyco:devfrom
Conversation
Contributor
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
Contributor
|
The following comment was made by an LLM, it may be inaccurate: Found a potential related PR: PR #14307: fix: use parentID matching instead of ID ordering for prompt loop exit and message rendering This appears to be addressing the same issue - replacing ID ordering with parentID matching for the prompt loop. This could be a duplicate or previous attempt at fixing the same problem. |
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Closes #17012
Type of change
What does this PR do?
Fixes an infinite assistant loop in web sessions.
SessionPrompt.loop()was using message ID ordering to decide whether the latest finished assistant message belonged to the latest user message:That is not reliable for web prompts, because the user
messageIDis generated in the browser while assistant message IDs are generated on the server.This change replaces that check with:
This is the correct relationship because
parentIDdirectly links an assistant message to the user message it answers.How did you verify your code works?
Added a regression test covering a web-style prompt flow where the user
messageIDis provided externally and does not sort safely against a later server-generated assistant message ID.Also verified locally that prompt processing stops after the first finished assistant response instead of creating repeated assistant messages for the same user prompt.
Screenshots / recordings
N/A
Checklist