Skip to content
This repository has been archived by the owner on Sep 18, 2023. It is now read-only.

why client.disconnect_ws() don't work? #166

Open
PoetGcc opened this issue Jul 14, 2023 · 4 comments
Open

why client.disconnect_ws() don't work? #166

PoetGcc opened this issue Jul 14, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@PoetGcc
Copy link

PoetGcc commented Jul 14, 2023

when i use client.disconnect_ws(),doesn't seem to work。After use client.disconnect_ws(),there is still log output every once in a while. The log like:

WARNING:root:Websocket closed with status None: None
ERROR:websocket:Connection to remote host was lost. - goodbye

@ading2210 ading2210 added the bug Something isn't working label Jul 17, 2023
@lyra-ai
Copy link

lyra-ai commented Jul 18, 2023

Having the same issue, needs constant reset.

@canxin121
Copy link
Contributor

I have refactored a new asynchronous Async-Poe-Client in modern ways based on httpx and websockets, and i added some new functions.It could be faster, more stable and more convenient.Try using this version.

@PoetGcc
Copy link
Author

PoetGcc commented Jul 23, 2023

I have refactored a new asynchronous Async-Poe-Client in modern ways based on httpx and websockets, and i added some new functions.It could be faster, more stable and more convenient.Try using this version.

ok。老哥,我试试

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants
@lyra-ai @PoetGcc @canxin121 @ading2210 and others