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
go: module github.com/cloudwego/iasm@upgrade found (v0.1.0), but does not contain package github.com/cloudwego/iasm/x86_64 #620
Comments
same situation,Maybe it's due to the #618 |
temporarily downgrade to version: v1.11.2 fix this error. |
"github.com/cloudwego/iasm" should be v0.0.9 |
The package "iasm" has always failed all it's tests: cloudwego/iasm#1 Edit: Which is why I don't think changing the version to v0.0.9 would help |
Please use this version of iasm: go get github.com/cloudwego/iasm@v0.0.9 Refer to cloudwego/kitex#1319 for more details. |
I see no reason or proof why that would work. All the tests in that package (even in version 0.0.9) are failing with this exact issue. |
The referred issue does not include any PRs. No working tests that might give us a measure of confidence. How do we know that changing the version actually solves the issue? |
Sorry for the inconvenience. This project is ported from a personal repository and we didn't pay attention to the workflow which is using go1.2 (not supported) and ARM64 (also not supported). The v0.0.9 is just the same as the original version and v0.1.0 introduced incompatible changes and was wrongly set as the latest release. We've removed v0.1.0 to avoid further confusion and will fix the workflow soon after. |
I have tested it and it does indeed resolve the issue. Thank you @felix021 |
I have imported |
@jurilucci-geoin bytedance 1.11.2 does not have this issue in the first place.
|
@jurilucci-geoin As is explained before, this issue can be solved by: go get github.com/cloudwego/iasm@v0.0.9 Refer to cloudwego/kitex#1319 for more details. |
Also experiencing this issue via gin:
|
TIPS: DON'T ALWAYS update your go mod using |
sorry, this issue can be solved by:
|
The text was updated successfully, but these errors were encountered: