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]: response text generated by a model sometimes disappears after computer/browser is woken up from a 'sleep' #1061

Open
2 tasks done
John-Harris opened this issue Jan 15, 2024 · 4 comments

Comments

@John-Harris
Copy link

Bug description

It's similar to the issue described here:
https://www.reddit.com/r/sveltejs/comments/oi4wpp/sveltekit_bug_data_from_store_dissapears_after_1/

The reddit user has provided a 'dynamic; screen shot (movie) of the issue. So annoying because sometimes many minutes have been invested in generating the model's response. Some models emit the generated response to the docker log file at completion so that's a help when they do that

Steps to reproduce

(This is not a guaranteed step-by-step to recreate the issue. It happens intermittently.)

Step 0: OS: Windows 10, Docker with WSL. serge-chat project

Step 1: Launch serge-chat in a browser, select 'new chat', select a model, provide a prompt

Step 2: Step away from the computer while serge/alpaca and the model generate a response

Step 3: Return to the computer, click the login button, desktop refreshes with browser and generated response visible.

Step 4: Suddenly the generated response is obliterated. Response text disappears.

Environment Information

OS: Windows 10
Docker desktop v4.26.1
serge-serge:latest

Screenshots

No response

Relevant log output

No response

Confirmations

  • I'm running the latest version of the main branch.
  • I checked existing issues to see if this has already been described.
@morpheus2448

This comment was marked as abuse.

@morpheus2448

This comment was marked as abuse.

@John-Harris
Copy link
Author

John-Harris commented Jan 23, 2024 via email

@John-Harris
Copy link
Author

This is not a critical issue. I was able to bypass it by setting my desktop computer to 'never sleep'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants