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

calling toString() on a connected UnixDomainSocket returns Socket[unconnected] #22

Open
inieves opened this issue Mar 23, 2022 · 1 comment · May be fixed by #44
Open

calling toString() on a connected UnixDomainSocket returns Socket[unconnected] #22

inieves opened this issue Mar 23, 2022 · 1 comment · May be fixed by #44

Comments

@inieves
Copy link

inieves commented Mar 23, 2022

I noticed that UnixDomainServerSocket returns useful information on a call to toString(), but it's friend UnixDomainSocket does not return useful information, it actually returns incorrect information:
Socket[unconnected]

More useful and correct output would be the path that was used to create the socket.

I have not tested the Win32NamedPipeSocket but I suspect a similar issue would occur.
@eed3si9n eed3si9n linked a pull request Sep 5, 2024 that will close this issue
Open
@eed3si9n
Copy link
Member

eed3si9n commented Sep 5, 2024

I guess toString is coming from the Socket class? Here's a PR to try to fix this - #44

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

Successfully merging a pull request may close this issue.

Implement toString eed3si9n/ipcsocket
2 participants
@eed3si9n @inieves