-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
path/filepath: Clean changed in Go 1.20 #58348
Comments
Looking back at the original failing test, I don't see why that should not use |
I see that this isn't documented, however. It should be. As of Go 1.20, we do a better job of identifying volume names, and we're more lax about accepting invalid volume names. I don't think this is a regression, since But we should fix the docs. |
@bhavyastar Better documentation is always welcome. Thanks. |
Change https://go.dev/cl/469955 mentions this issue: |
Fixes golang#58348 Change-Id: I4aac0285f11618a45aca6b13c2da2a10a803a9b5 Reviewed-on: https://go-review.googlesource.com/c/go/+/469955 Reviewed-by: Bryan Mills <bcmills@google.com> Auto-Submit: Damien Neil <dneil@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Damien Neil <dneil@google.com>
I have some GitHub action tests that started to fail on Windows after I bumped the build matrix to Go 1.20.
I have distilled the issue into this small repo: https://github.com/bep/go120winpathregression
I have looked closely in the release notes for Go 1.20 about this, but that does not mention this change. Also, the GoDoc for
filepath.Clean
is pretty clear about what happens to "multiple Separator elements":The text was updated successfully, but these errors were encountered: