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

关于使用此组件连接火山大模型出现自动断开的问题。 (IDFGH-14226) #712

Open
3 tasks done
PoohWoah opened this issue Dec 13, 2024 · 2 comments
Open
3 tasks done
Labels

Comments

@PoohWoah
Copy link

Answers checklist.

  • I have read the documentation for esp-protocols components and the issue is not addressed there.
  • I have updated my esp-protocols branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

What component are you using? If you choose Other, provide details in More Information.

esp_websocket_client

component version

1.3.0

IDF version.

5.3.1

More Information.

目前我在使用esp32idf库的ws组件与大模型服务器进行一个连接,用来识别我的流式语音,目前出现连接后自动就会断开
W (9150) transport_ws: esp_transport_ws_poll_connection_closed: unexpected data readable on socket=54 W (9151) websocket_client: Connection terminated while waiting for clean TCP close

这是报错,因为我用postman是可以正常持续连接,所以我的url和帧头是没有问题的,目前我怀疑是esp的ws库连接服务器时发送了什么消息给服务器从而被断开了?

@PoohWoah
Copy link
Author

可能不是bug,我标签选择的时候选择错误了

@github-actions github-actions bot changed the title 关于使用此组件连接火山大模型出现自动断开的问题。 关于使用此组件连接火山大模型出现自动断开的问题。 (IDFGH-14226) Dec 13, 2024
@espressif-bot espressif-bot added the Status: Opened Issue is new label Dec 13, 2024
@david-cermak
Copy link
Collaborator

Hi @PoohWoah

This message

W (9150) transport_ws: esp_transport_ws_poll_connection_closed: unexpected data readable on socket=54
W (9151) websocket_client: Connection terminated while waiting for clean TCP close

appears in the log if close handshake failed to complete, but it also appears after the closure was started. I cannot tell if the closure was initiated by the client or the server.
could you please share debug logs from this event? (and ideally also a wireshark capture, so we know exactly who initiated the close and why)

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

No branches or pull requests

3 participants