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.

Sign up for GitHub

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

Jump to bottom

W/Failed to close socket on proxy side: {}. It seems client have already closed connectioshutdown failed: ENOTCONN (Transport endpoint is not connected) #316

Open
lk2017 opened this issue Sep 1, 2023 · 2 comments
Open

W/Failed to close socket on proxy side: {}. It seems client have already closed connectioshutdown failed: ENOTCONN (Transport endpoint is not connected) #316

lk2017 opened this issue Sep 1, 2023 · 2 comments

Comments

@lk2017
Copy link

lk2017 commented Sep 1, 2023

I user the lib with example code, there is a certain probability of errors like the title, about 30%, how can I solve this problem?
@Qdafengzi
Copy link

same error ,feel this project have dead

@Qdafengzi
Copy link

I user the lib with example code, there is a certain probability of errors like the title, about 30%, how can I solve this problem?

this solved ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Qdafengzi @lk2017