Repository navigation
Timestamp synthetic messages in the packaged conversation smoke - #8297
huangruiteng wants to merge 1 commit into
Conversation
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
|
This pull request has merge conflicts with Choose the remote for the base repository, not an out-of-date fork. git fetch upstream
git rebase upstream/main
# Resolve each conflict, git add the resolved files, then git rebase --continue.
git push --force-with-lease origin HEADFor a same-repository clone whose Keep the DCO |
The installed conversation activity smoke can reach the error boundary while switching from the steward conversation to Goal Chat. Its simulated completion and queued user messages omitted the timestamp that the chat store writes for every visible message. Transcript sorting then called
localeCompareon an undefined value.Give both fixture messages the required
created_atfield. The existing assertions still exercise the Goal send and the original turn observer.Validation
32167518b3c2646fd9b6a3a6e0aaf74b258a7b70under Python 3.11. The original fixture timed out at the Goal send after the transcript sorting exception.conversation-activityscenario passed.