java.io.IOException: ConnectNamedPipe() failed with: 535 about ipcsocket HOT 6 CLOSED

Thanks for the report. We now have JNA and JNI implementations (for GraalVM JNI works better) so I wonder if the check is done one but not the other.

from ipcsocket.

@eed3si9n I searched in the source code and this looks somewhat suspicious. Do you think it's intentional?

  @Override
  public int ERROR_PIPE_CONNECTED() {
    return WinError.ERROR_NO_DATA;
  }

from ipcsocket.

I am guessing that was a typo? /cc @eatkins

from ipcsocket.

Definitely looks like a typo. @dolly2 can you work around the problem with sbt -Dsbt.ipcsocket.jni=true? That should toggle the server to use the JNI implementation that theoretically should not hit the typo.

from ipcsocket.

@eatkins Using JNI explicitly resolved the issue for me. Thanks for workaround!

from ipcsocket.

This was fixed in #21

from ipcsocket.