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

cmd/cue: export cannot write to a named pipe using --outfile #3631

Open
jpluscplusm opened this issue Dec 23, 2024 · 0 comments
Open

cmd/cue: export cannot write to a named pipe using --outfile #3631

jpluscplusm opened this issue Dec 23, 2024 · 0 comments
Labels
NeedsInvestigation Triage Requires triage/attention

Comments

@jpluscplusm
Copy link
Collaborator

What version of CUE are you using (cue version)?

$ cue version
cue version v0.11.0

go version go1.23.3
      -buildmode exe
       -compiler gc
       -trimpath true
     CGO_ENABLED 0
          GOARCH amd64
            GOOS linux
         GOAMD64 v1
cue.lang.version v0.11.0

Does this issue reproduce with the latest stable release?

I suspect so; v0.11.1 doesn't appear to contain any changes in this area.

What did you do?

exec mkfifo aPipe
exec cat aPipe &
exec cue export file.cue --outfile=aPipe --out json
-- file.cue --
x: 1

What did you expect to see?

A passing testscript.

What did you see instead?

> exec mkfifo aPipe
> exec cat aPipe &
> exec cue export file.cue --outfile=aPipe --out json
[stderr]
error writing "aPipe": file already exists
[exit status 1]
FAIL: /tmp/testscript1911196150/fifo.txtar/script.txtar:3: unexpected command failure
[background] cat aPipe: signal: interrupt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Triage Requires triage/attention
Projects
None yet
Development

No branches or pull requests

1 participant