oobabooga / text-generation-webui

A Gradio web UI for Large Language Models.
GNU Affero General Public License v3.0
40.57k stars 5.31k forks source link

Not sure what is going on here. #3948

Closed Herman5555 closed 1 year ago

Herman5555 commented 1 year ago

Describe the bug

Haven't had any issues with ooba before but a recent update has caused random severe repetition issues with this error that is responsible I believe. I have reinstalled with the auto installer with the same result, all settings were the same as always and were working fine. Can anyone tell me what's going on here please?.

Is there an existing issue for this?

Reproduction

Fresh install of ooba, here are my launch commands, connecting to Sillytavern, everything works fine until it doesn't randomly all of a sudden. I'm using Exllama HF as a loader with default settings running a 4k context llama 2 model.

--api --auto-launch

I also have api extension enabled.

Screenshot

No response

Logs

Traceback (most recent call last):
  File "C:\oobabooga_windows\installer_files\env\lib\site-packages\websockets\legacy\server.py", line 240, in handler
    await self.ws_handler(self)
  File "C:\oobabooga_windows\installer_files\env\lib\site-packages\websockets\legacy\server.py", line 1186, in _ws_handler
    return await cast(
  File "C:\oobabooga_windows\text-generation-webui\extensions\api\streaming_api.py", line 89, in _handle_connection
    await _handle_stream_message(websocket, message)
  File "C:\oobabooga_windows\text-generation-webui\extensions\api\util.py", line 148, in api_wrapper
    return await func(*args, **kwargs)
  File "C:\oobabooga_windows\text-generation-webui\extensions\api\streaming_api.py", line 39, in _handle_stream_message
    await websocket.send(json.dumps({
  File "C:\oobabooga_windows\installer_files\env\lib\site-packages\websockets\legacy\protocol.py", line 635, in send
    await self.ensure_open()
  File "C:\oobabooga_windows\installer_files\env\lib\site-packages\websockets\legacy\protocol.py", line 944, in ensure_open
    raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedOK: received 1005 (no status code [internal]); then sent 1005 (no status code [internal])

System Info

Windows 10 pro 64x
NVIDIA RTX 3060ti 8gb
Ph0rk0z commented 1 year ago

That is your server disconnecting.

BadisG commented 1 year ago

I have the same error, did someone manage to fix this?

Gitikara commented 1 year ago

Just adding in that I'm also still experiencing this error. Mine still works afterward and it's not preventing use, so it's probably not an urgent bug... but it was alarming to see all the red text, and I don't know enough to know if it has any performance impact in any regard.

github-actions[bot] commented 1 year ago

This issue has been closed due to inactivity for 6 weeks. If you believe it is still relevant, please leave a comment below. You can tag a developer in your comment.