We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Please answer these questions before submitting your issue. Thanks!
go version
go env
If possible, provide a recipe for reproducing the error. A complete runnable program is good. A link on play.golang.org is best.
According to http://pubs.opengroup.org/onlinepubs/009695399/functions/lseek.html: lseek returns ESPIPE on pipe.
However, current implementation use EPIPE instead.
go/src/syscall/syscall_windows.go
Lines 350 to 352 in eaa198f
ESPIPE
EPIPE
The text was updated successfully, but these errors were encountered:
It's hard to get too excited about this, since we made up EPIPE anyhow for Windows. But if you want to send a patch I suppose it's OK with me.
Sorry, something went wrong.
CL https://golang.org/cl/41311 mentions this issue.
ffd7cfc
No branches or pull requests
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
According to http://pubs.opengroup.org/onlinepubs/009695399/functions/lseek.html:
lseek returns ESPIPE on pipe.
However, current implementation use EPIPE instead.
go/src/syscall/syscall_windows.go
Lines 350 to 352 in eaa198f
What did you expect to see?
ESPIPE
What did you see instead?
EPIPE
The text was updated successfully, but these errors were encountered: