@rotor can you reproduce the issue? If yes, then we can try to find out which syscall caused it. This may be a bug in Go after all…
@rotor can you reproduce the issue? If yes, then we can try to find out which syscall caused it. This may be a bug in Go after all…