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

x/playground: web app runtime error with file/dir name conflicts in the txtar #44678

Open
yaegashi opened this issue Feb 28, 2021 · 2 comments · May be fixed by golang/playground#11
Open

x/playground: web app runtime error with file/dir name conflicts in the txtar #44678

yaegashi opened this issue Feb 28, 2021 · 2 comments · May be fixed by golang/playground#11
Labels
NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@yaegashi
Copy link

What did you do?

Run the following in the Go Playground: https://play.golang.org/p/92soX8Gyrsn

package main

func main() {}
-- a --
-- a/b --

What did you expect to see?

It should tell there's a file/dir name conflict in the txtar.

What did you see instead?

Error communicating with remote server.
Program exited.

Addtional info

The playground web app emits either of the following runtime errors when there's a file/dir name conflict:

cmdFunc error: mkdir /tmp/sandbox253661173/a: not a directory
cmdFunc error: error creating temp file "/tmp/sandbox446449006/a": open /tmp/sandbox446449006/a: is a directory
@gopherbot gopherbot added this to the Unreleased milestone Feb 28, 2021
@gopherbot
Copy link

Change https://golang.org/cl/297369 mentions this issue: playground: check file/dir name conflicts in txtar

@dmitshur dmitshur added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Mar 2, 2021
@dmitshur
Copy link
Contributor

dmitshur commented Mar 2, 2021

CC @golang/release.

@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants