-
Notifications
You must be signed in to change notification settings - Fork 2k
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
io/fs: package io/fs is not in GOROOT #1161
Comments
👋 Thanks for reporting! A maintainer will take a look at your issue shortly. 👀 In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues. ⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9 📣 If you've already given us your feedback, you can still help by spreading the news, https://twitter.com/sagikazarmark/status/1306904078967074816 Thank you! ❤️ |
The CI runs against Go 1.15. I can't reproduce it locally either:
|
Hey @sagikazarmark This does not happen on a It just fails on |
Same issue. Going to rollback to 1.7.1 |
@arriqaaq I can't reproduce it with |
Same issue here. But just infects |
Same issue here with v 1.8.0 and goland version 1.15 |
Same here, to reproduce create a new module as above and then add a main.go file importing and using viper. Run the example and then try to tidy/why to see the issue happening.
|
I'm able to reproduce this issue on Go 1.15.5, but I can no longer reproduce it after Go 1.15.10, so upgrading to that (or later) version should fix the problem. References: |
@arriqaaq @kotyara85 @tmac33 @rengas @moreandres Can someone confirm that upgrading to 1.15.10 resolves the issue? |
yes, upgrading can resolve this. |
Cool! Please upgrade to a newer version then. |
Upgrade to go1.15.10 to solve this? |
@DarthPestilane you could try replacing the afero version. I don't think we use anything from the new 1.6.0 release:
Keep in mind that Viper (similarly to Go itself) supports the two latest minor Go versions. (Yes, the readme is incorrect and needs updating) |
upgrade to go version go1.16.6 solve the problem. |
Having the same error with go1.16.7 go get github.com/spf13/viper@v1.8.1 github.com/spf13/viper imports |
…es). This is due to the following bug which causes build failures: spf13/viper#1161
Per spf13/viper#1161, this issue has already been fixed. `github.com/spf13/viper` is okay to. upgrade at this point.
Per spf13/viper#1161, this issue has already been fixed. `github.com/spf13/viper` is okay to. upgrade at this point. Signed-off-by: Antonette Caldwell <pullmana8@gmail.com>
Expected behavior (what you expected to happen):
go mod tidy
to work when viper 1.8.0 is importedActual behavior (what actually happened):
Fails with the error:
Environment:
The text was updated successfully, but these errors were encountered: