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.

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

os, syscall: Seek on pipe on windows doesn't return ESPIPE #20066

Closed
hirochachacha opened this issue Apr 21, 2017 · 2 comments
Closed

os, syscall: Seek on pipe on windows doesn't return ESPIPE #20066

hirochachacha opened this issue Apr 21, 2017 · 2 comments

Comments

@hirochachacha
Copy link
Contributor

@hirochachacha hirochachacha commented Apr 21, 2017

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.

if ft == FILE_TYPE_PIPE {
return 0, EPIPE
}

What did you expect to see?

ESPIPE

What did you see instead?

EPIPE

@ianlancetaylor
Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Apr 21, 2017

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.

@ianlancetaylor ianlancetaylor added this to the Unplanned milestone Apr 21, 2017
@gopherbot
Copy link

@gopherbot gopherbot commented Apr 21, 2017

CL https://golang.org/cl/41311 mentions this issue.

@gopherbot gopherbot closed this in ffd7cfc Apr 22, 2017
@golang golang locked and limited conversation to collaborators Apr 22, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.