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] #635

Open
wzr1337 opened this issue Dec 9, 2024 · 1 comment
Open

[BUG] #635

wzr1337 opened this issue Dec 9, 2024 · 1 comment
Labels
needs investigation Bug but cause is not identified.

Comments

@wzr1337
Copy link
Contributor

wzr1337 commented Dec 9, 2024

🚨 Please Note 🚨

To ensure efficient investigation of the issue, please fill out the fields below with as much detail as possible. Reports that do not follow this template may be closed without notification. We appreciate your cooperation.

Describe the bug

The WebSocket connection delivers chunks very slowly until it fails sending at all. Depending on where in the process the connection failed, you can refresh the page most of the time and the GET request will retrieve the full conversation correctly. I have already increased the RAM settings on the websocket handler lambda, but it does not seem too improve the situation.

To Reproduce

Steps to reproduce the behavior:

  1. Run any larger conversation
  2. wait for the failure to happen
  3. Refresh the page
  4. See that the convo is complete, even though the connection broke before
@Yukinobu-Mine
Copy link
Contributor

@wzr1337 Can you provide a video of this issue occurring?

@Yukinobu-Mine Yukinobu-Mine added the needs investigation Bug but cause is not identified. label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs investigation Bug but cause is not identified.
Projects
None yet
Development

No branches or pull requests

2 participants