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: ReadDir in freebsd 14.1 can not list if path have chinese char #71326

Open
runsys opened this issue Jan 19, 2025 · 15 comments
Open

os: ReadDir in freebsd 14.1 can not list if path have chinese char #71326

runsys opened this issue Jan 19, 2025 · 15 comments
Labels
BugReport Issues describing a possible bug in the Go implementation. OS-FreeBSD WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@runsys
Copy link

runsys commented Jan 19, 2025

Go version

go 1.21 amd64

Output of go env in your module/workspace:

no change

What did you do?

OS.ReadDir use Chinese char path.I have test many paths. it is a real bug.

What did you see happen?

it can not return file and folder.

What did you expect to see?

return rightly.

@runsys
Copy link
Author

runsys commented Jan 19, 2025

if path no Chinese char t it can return have Chinese char files.

@seankhliao
Copy link
Member

Please include the information requested in the bug report, a reproducer, and the actual error message (and FreeBSD version information as well).
Note that 1.21 is no longer a supported version of Go.

@seankhliao seankhliao added OS-FreeBSD WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Jan 19, 2025
@seankhliao seankhliao changed the title os.ReadDir in freebsd 14.1 can not list if path have chinese char os: ReadDir in freebsd 14.1 can not list if path have chinese char Jan 19, 2025
@runsys
Copy link
Author

runsys commented Jan 19, 2025

No description provided.

@runsys
Copy link
Author

runsys commented Jan 19, 2025

IMG_20250119_204819.jpg

print error output

@gabyhelp gabyhelp added the BugReport Issues describing a possible bug in the Go implementation. label Jan 19, 2025
@seankhliao seankhliao added WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. and removed WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Jan 19, 2025
@runsys
Copy link
Author

runsys commented Jan 19, 2025

go 1.23.5 have same error.

@seankhliao seankhliao added WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. and removed WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. labels Jan 20, 2025
@ianlancetaylor
Copy link
Member

Please show us how to recreate the problem. For example, please show us the contents of a directory as printed by /bin/ls, please show us a program, and please show us the output of that program. Please show all of this as plain text, not as an image. There is no reason to use an image to show plain text data.

@runsys
Copy link
Author

runsys commented Jan 21, 2025

文件夹.zip

example. I have tested zfs ntfs. they have same error.

@runsys
Copy link
Author

runsys commented Jan 21, 2025

the ls output is right.

@wingrez
Copy link
Contributor

wingrez commented Jan 21, 2025

请展示一个可以复现问题的最简代码,并将错误的输出以文字的形式展示出来(而不是拍照)

Show a code that can reproduce the problem and display the error output in text.

@runsys
Copy link
Author

runsys commented Jan 21, 2025

_,er:=os.ReadDir("/root/文件夹/")
panic(er)

@ianlancetaylor
Copy link
Member

I'm sorry, that zip file does not tell me anything.

Please show a complete Go program that demonstrates the problem. Please show the complete output of that Go program. Thanks.

@runsys
Copy link
Author

runsys commented Jan 21, 2025

the output enough to describle the question.need no more.

@ianlancetaylor
Copy link
Member

We can't fix this bug without more information.

I don't even understand what the bug is.

@runsys
Copy link
Author

runsys commented Jan 22, 2025

after I repaired file system.and reboot system. the question is still there. compare with ls output the return count is different.ls output no error.and in Windows the count is different with the two.20250122_081118_edited.jpg

@ianlancetaylor
Copy link
Member

Please paste plain text as plain text. Please do not use images. Images are much harder to read. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BugReport Issues describing a possible bug in the Go implementation. OS-FreeBSD WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

5 participants