Skip to content

io: Copy leaves file zero bytes in Azure with CIFS #67806

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.

Sign up for GitHub

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

Jump to bottom
Closed
jack-edgar-bi opened this issue Jun 4, 2024 · 2 comments
Closed

io: Copy leaves file zero bytes in Azure with CIFS #67806

jack-edgar-bi opened this issue Jun 4, 2024 · 2 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone
Backlog

Comments

@jack-edgar-bi
Copy link

Go version

1.22.3

Output of go env in your module/workspace:

I'm using the golang:1.22.3 Docker image.

What did you do?

Please see #42400 but I am still seeing this issue with v1.22.3, when using an Azure Container Apps mount, which runs on AKS and uses a CIFS share.

What did you see happen?

Please see #42400, but essentially no bytes are written to the target file, even after flush/close. The file is successfully created, but io.copy transfers no contents.

What did you expect to see?

The file should be populated, which does occur for the same application when run locally.
@mknyszek mknyszek added this to the Backlog milestone Jun 4, 2024
@mknyszek mknyszek added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Jun 4, 2024
@seankhliao seankhliao added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Jun 4, 2024
@mknyszek
Copy link
Contributor

mknyszek commented Jun 7, 2024

Unfortunately without additional information it's difficult to discern what the problem is exactly, especially if it seems to work fine for you locally.

Note that io.Copy is just using the Read and Write methods of its arguments. If one of them is specific to the Azure SDK, it's unlikely to be a Go project issue. (io.Copy is not a very complex function, and it has not changed recently, so I don't see why it wouldn't simply work, other than the Read and Write methods it's using have some problems.)

@gopherbot
Copy link
Contributor

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@gopherbot gopherbot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@mknyszek @gopherbot @seankhliao @jack-edgar-bi