-
Notifications
You must be signed in to change notification settings - Fork 18k
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
plugin: reject plugins built with a different version of the toolchain #17832
Comments
CL https://golang.org/cl/33161 mentions this issue. |
Hi, I've cherry picked this change and built tip and now every time I get mismatch for the "runtime" package on macOS: |
What version of macOS? |
Ok, I've been able to distill minimal reproducible test from my case. It turns out that plugin fails to load when loaded via I've created repository https://github.com/wendigo/go-plugin-33161 showing this behaviour. Hope this helps :) |
Updating yesterday comment: I've tested it on newest tip version (b687d6a) with cherry-picked change #33161. ./all.bash is ok (no failing tests). macOS version is
|
I believe in-package tests are a particularly gnarly corner-case, and so I've punted it to #17928. (I don't believe that needs to be fixed for 1.8.) |
@crawshaw The fix for this seems to have caused the linux-amd64-noopt builder to start failing. Can you please take a look? |
Can't we handle this on the new bug we have for this: #17937? I'll try to find some time this weekend. |
Absolutely, I didn't see the new bug. Thanks. |
We should explicitly reject an attempt to open a plugin that was created by a different version of the Go toolchain. We have no reliable way to make that work, as the internal runtime package interface changes between versions. (I didn't see an explicit check for this--I may have missed one.)
The text was updated successfully, but these errors were encountered: