-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
Gomplate v3.11.x Go 1.21 panic: go4.org/unsafe/assume-no-moving-gc #1872
Comments
@erharb are you building |
Company security controls mostly, we have our own goproxy for scanning and handling go mods/installs. Usually it's just more paperwork to bring in pre-compiled binaries built from the internet, as opposed to just building it in-house where possible for our internal usage. I wanted to start with a "stable" released version first since we're evaluating using gomplate for use with GitHub Template repositories, though I'll definitely give v4 a shot soon! |
Confirmed using v4 similar to here is a sufficient workaround. |
@hairyhenderson I maintain the gomplate package for nixos and this same issue currently breaks it. I'd love to upgrade to v4 but the latest released version is v3.11.5... will v4 be released soon? (I'd rather not go to the hoops necessary to build from git if possible, mainly because I'd have to investigate what those hoops are exactly). |
I have some vacation time coming up next week, so I'll try to get a "clean" 3.11.6 released then. v4 is still a ways out - I just haven't had the free time to dedicate to it for a while 😞 |
Thanks @hairyhenderson - for the moment I've updated the package to force using go 1.20. Unfortunately I'm not much of a go programmer, so I can't be of much help on the actual issue :( |
Fixed by #1910 - I'll release 3.11.6 soon... |
That's great - thanks @hairyhenderson !! |
Same as PR #1796 except that was only addressed in v4. Since v4 is not yet a stable release I think it should be ported back to the
3.11.x
branch as well.The solution should be to update the module to the version indicated in the PR. I may have to first seek approval to contribute from my org, so if someone beats me to it so be it!
The text was updated successfully, but these errors were encountered: