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

do not throw a SOCKET-NOT-OPEN error when running a socket callback after the socket was closed #4795

Closed
davidnich opened this issue Sep 20, 2023 · 0 comments
Closed

do not throw a SOCKET-NOT-OPEN error when running a socket callback after the socket was closed #4795

davidnich opened this issue Sep 20, 2023 · 0 comments
Assignees
@davidnich
Labels
bug c++ fixed
Projects
Qore Development
Milestone
2.0

Comments

@davidnich
Copy link
Contributor

this is a normal situation if the remote end has already closed the socket
@davidnich davidnich added this to the 2.0 milestone Sep 20, 2023
@davidnich davidnich added this to To do in Qore Development via automation Sep 20, 2023
@davidnich davidnich self-assigned this Sep 20, 2023
davidnich added a commit that referenced this issue Sep 20, 2023
@davidnich
refs #4795 fixed executing socket callbacks after the socket is closed
a543603
davidnich added a commit that referenced this issue Sep 20, 2023
@davidnich
refs #4795 fixed executing socket callbacks after the socket is closed
358c910
davidnich added a commit that referenced this issue Sep 20, 2023
@davidnich
refs #4795 eliminated a spurious exception when calling socket callba…
94fb6d6 
…cks after a connection was closed

updated to v2.0.0
davidnich added a commit that referenced this issue Sep 20, 2023
@davidnich
refs #4795 fixed executing socket callbacks after the socket is closed
0c40e85
Qore Development automation moved this from To do to Done Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@davidnich davidnich

Labels
bug c++ fixed
Projects
Qore Development
Done
Milestone
2.0
Development

No branches or pull requests
1 participant
@davidnich