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: When flooding, some messages in the middle fail to send. #506

Closed
wxuanF opened this issue Jan 26, 2024 · 3 comments
Closed

Bug: When flooding, some messages in the middle fail to send. #506

wxuanF opened this issue Jan 26, 2024 · 3 comments
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@wxuanF
Copy link

wxuanF commented Jan 26, 2024

What happened?

When flooding, some messages in the middle fail to send.
image

Upon re-entering the group chat after flooding, the messages that failed to send are not visible (Upon re-entering the group chat after flooding, it is unclear whether the messages have disappeared or if the exclamation marks indicating failure are missing.).

What did you expect to happen?

.

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

.

Anything else we need to know?

No response

version

```console $ {name} version # paste output here ```

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

@wxuanF wxuanF added the bug Categorizes issue or PR as related to a bug. label Jan 26, 2024
@kubbot
Copy link
Contributor

kubbot commented Mar 26, 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 Mar 26, 2024
@kubbot
Copy link
Contributor

kubbot commented Apr 2, 2024

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

@kubbot kubbot closed this as completed Apr 2, 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
@FGadvancer
Copy link
Member

The issue is caused by SQLite's concurrency limitations. When the message reception speed is too high, database access concurrency increases, leading to db is locked errors. The SDK has now added a global read-write lock at the application layer to prevent this issue.

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
Development

No branches or pull requests

3 participants