Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: After clearing the sqllite cache, loading the chat history for the first time when opening a group session will trigger 100% of the loaded history messages to return an incorrect value. #179

Closed
MyCupOfTeaOo opened this issue Jul 28, 2023 · 5 comments · Fixed by #773
Assignees
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@MyCupOfTeaOo
Copy link

What happened?

image
use sdk getAdvancedHistoryMessageList interface
isEnd is false when all history message is loaded

What did you expect to happen?

isEnd is false when no history message

How can we reproduce it (as minimally and precisely as possible)?

  1. clearing the sqllite cache
  2. open a group session
  3. call getAdvancedHistoryMessageList

Anything else we need to know?

No response

version

wasm v3.0.0
server v3.0.0

Cloud provider

OS version

```console # On Linux: $ cat /etc/os-release # paste output here $ uname -a # paste output here # On Windows: C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture # paste output here ```

Install tools

@MyCupOfTeaOo MyCupOfTeaOo added the bug Categorizes issue or PR as related to a bug. label Jul 28, 2023
@FGadvancer FGadvancer self-assigned this Aug 29, 2023
@FGadvancer FGadvancer pinned this issue Aug 29, 2023
@kubbot
Copy link
Contributor

kubbot commented Oct 29, 2023

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot kubbot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 29, 2023
@kubbot
Copy link
Contributor

kubbot commented Nov 5, 2023

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as completed Nov 5, 2023
@FGadvancer FGadvancer reopened this Nov 20, 2023
@FGadvancer
Copy link
Member

Due to the involvement of backend server fixes related to message fetching logic, this issue will be fixed in a later version. In the meantime, you can determine whether you have reached the end of messages by checking if the number of messages fetched in a page is zero.

@kubbot kubbot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 20, 2023
@kubbot
Copy link
Contributor

kubbot commented Jan 20, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot kubbot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2024
@kubbot
Copy link
Contributor

kubbot commented Jan 28, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as completed Jan 28, 2024
@github-actions github-actions bot reopened this Aug 8, 2024
@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
3 participants