-
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
x/text: tag new release #51822
Comments
please include the go env output |
Looks like cc @mpvl @golang/release |
The above were fixed by https://go-review.googlesource.com/c/text/+/304029, I think. I think we're all good to do a release soon? cc @rolandshoemaker |
@mvdan @rolandshoemaker |
Agree. Closing then. |
What version of Go are you using?
Does this issue reproduce with the latest release?
yes
Does this issue reproduce with go 1.17.8?
no
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I was trying to create translations for my Go (fiber) project, at first I thought this was an issue related to Fiber.
So I created a new empty project, started all over (without Fiber), and got the same error.
The tutorial I was following: https://www.alexedwards.net/blog/i18n-managing-translations
Then I realised that I've updated Go last week, so I downgraded my Go version to 1.17, and everything worked again.
What I saw when I my Go version was at 1.18:
How to reproduce?
This is the repo for my project: https://github.com/Joris1Jansen/SimpleNotesApi/tree/GOLANG-ISSUE_WITH_GOTEXT
Please, don't look at the complete mess of my code, this is a project I'm trying out all new things I want to learn.
The current version in
go.mod
is1.17
, so everything should work now.Should return something like:
BUT, if we upgrade to
go version 1.18
We get a big output, but the main isseu:
I hope that this is enough information, this is my first time opening an issue/bug. So feel free to provide me with any feedback to learn from for the next time.
Cheers
The text was updated successfully, but these errors were encountered: