opa
opa copied to clipboard
open-policy-agent
Update our wasmtime
We're far behind... It's causing issues for the alpine package build, too. Besides missing out on new features and improvements.
Tried it in https://github.com/open-policy-agent/opa/pull/6556 but hit some build problems on windows.
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
At the time of writing this comment, the latest version of wasmtime-go is v28.
I attempted to upgrade wasmtime-go to v28 in my forked repository, but the Windows build also failed. Here are the job logs: go-build-windows-amd64-logs.txt.
From the logs, it appears that the MinGW compiler is incompatible with the newer version of wasmtime-go. Unfortunately, the CI logs from PR https://github.com/open-policy-agent/opa/pull/6556 have expired, so I can't compare the errors directly. However, I suspect they are quite similar.
/usr/bin/x86_64-w64-mingw32-ld: /src/vendor/github.com/bytecodealliance/wasmtime-go/v28/build/windows-x86_64/libwasmtime.a(07c0bb04dd2aaef1-helpers.o):helpers.c:(.text$wasmtime_setjmp_inverted+0x26): undefined reference to `__intrinsic_setjmpex'
Similar issues have been reported in the wasmtime-go repository:
- https://github.com/bytecodealliance/wasmtime-go/issues/192
- https://github.com/bytecodealliance/wasmtime-go/pull/195/commits/227ba15cc1a804861c1d9fa28b66bdf03be0394d
Reading up on that thread, I guess this is a starting point: https://github.com/bytecodealliance/wasmtime-go/issues/192#issuecomment-1734252302 -- so we'd need to check mingw versions and see if we can make them match in OPA's build toolchain.
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue.
I think we need to do this. Right now, it's just so outdated, it's becoming problematic. 😬
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue.