Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Unix sockets are not implemented #134
Comments
|
Unix sockets are partially implemented, and they do work. The socket files just don't show up in the file system. However, it's still possible to connect to them if you know the path of the socket file. Of course, this does break applications that attempt to "stat" a socket file or do anything else that depends on the file being present. We're working to address this issue. |
|
As @SvenGroot mentions, file system integration of UNIX sockets is not complete yet. We will be tracking\prioritizing which features to light up next by looking at the feedback provided at the wpdev portal. We appreciate your feedback and please make sure to provide it through the wpdev portal as well. |
sunilmut
closed this
Apr 11, 2016
This was referenced Apr 14, 2016
sunilmut
reopened this
Apr 18, 2016
willingc
referenced this issue
in jupyter/notebook
Apr 21, 2016
Open
python2 kernel death in Ubuntu on Windows #1331
MadcowD
commented
May 1, 2016
•
|
@SvenGroot @sunilmut Just an update I can reproduce the issue referenced with #1331. Jupyter notebook is using sockets and getting Invalid argument (src/tcp_address.cpp:186). Further investigation led me to find that I built libzmq and got the following log from the test suite. All of the errors point to the same line of code.
Related #69 |
This was referenced May 1, 2016
|
Adding link to source code exhibiting an issue: Microsoft#207 |
This was referenced Aug 29, 2016
lypanov
commented
Nov 10, 2016
•
|
This AFAICT also breaks Rails 5 out of the box without the hack of disabling of spring (it's simply too slow at times without Spring so this is really painful). Any news on this? |
janbernloehr
referenced this issue
Nov 19, 2016
Closed
Subscribing & Publishing from ROS nodes does not work #1391
jackchammons
added
bug
network
labels
Dec 13, 2016
mindplay-dk
referenced this issue
Apr 10, 2017
Closed
Errors galore during apt-get dist-upgrade #1851
mindplay-dk
commented
Apr 10, 2017
|
This may be what's breaking the default socket-based configuration with NGINX and PHP-FPM? I was able to get it to run reliably only after configuring it to use TCP instead of sockets, and also failed to use sockets with PHP, is this all related to this issue? Is there a fix on the way, or is this very far off? I really want to use UOW for development on my Windows system, mainly because there are features (such as sockets, threads and readline support) that are unavailable in Windows-builds of PHP. |
|
Could someone on the WSL team perhaps summarize what they believe to be the status of this issue? I have personally used UNIX Sockets without any issue. But I haven't done anything fancy with them. I realize it's more complicated than a simple "works" vs "not works" -- there are lots of flags and options and whatnot that you can set on a socket that affect its behavior; my understanding is that some work and some do not. |
|
@aseering - We are not aware of any open issues with the WSL AF_UNIX socket implementation. But, I know it's not fully compatible yet because for example the @mindplay-dk - Thanks for your post. We will have to take one issue at a time, so that we can root cause and fix it. Can you please post repro steps, build number and strace, if possible? You can see the template here. To gather strace, use |
|
Regarding capturing an strace, the challenge here will presumably be identifying what command to run. (The "command" in this case is two separate backgrounded system services, nginx and php-fpm; both would need to be run directly and in the foreground.) @mindplay-dk -- I think you indicated on #1851 that you weren't sure how to accomplish that level of Linux magic? I can try to take a look, but I may not get to it for a while. If anyone else is following this thread and would be willing to give it a shot, please do. |
|
@sunilmut -- thanks! The title of this ticket implies that UNIX sockets don't work at all. And the ticket is still open. Up to you, but I wonder if some ticket-wrangling might be in order? :-) |
|
@aseering - Makes sense. I will close this issue out, it's too broad and not actionable. @mindplay-dk - We will continue to work with you on the other issue. As for the strace, we would have to then rely on the repro. |
sunilmut
closed this
Apr 10, 2017
mindplay-dk
commented
Apr 11, 2017
|
@sunilmut I know you closed this issue, but not sure where else to answer the questions you asked. (?) To help you repeat the php-pm issue, here's the sandbox project for testing: https://bitbucket.org/mindplaydk/http-bench This project has a bunch of different scripts that all do the same thing - return a JPEG image - in different ways, because I'm using it to benchmark and evaluate the performance of various means of sending an image. Clone the project locally. Run Run The relevant changes for the php-pm setup happened in this commit and the only thing I wrote really was this simple front controller which does nothing except return the image, it doesn't even care what the Request looks like at all. Quick and dirty. I posted steps to recreate my environment here. I'm on Windows 10 Pro version 1703 build 15063.13 I tried to run that "strace" you asked for, so, this:
It produced these files. I think that's everything you asked for - let me know if there's anything else I can do? |
mindplay-dk
commented
Apr 11, 2017
|
(oh, and I guess |
guineawheek commentedApr 11, 2016
socket() works, but bind() doesn't create the actual socket file.
This kills things like wine and ssh-agent.