Skip to content
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

Non-specifed dependency on op-program using go runtime <= 1.22 #13447

Open
BlocksOnAChain opened this issue Dec 17, 2024 · 0 comments
Open

Non-specifed dependency on op-program using go runtime <= 1.22 #13447

BlocksOnAChain opened this issue Dec 17, 2024 · 0 comments
Labels
MT cannon - audit findings grouping for audit findings MT cannon - Mainnet relevant issues needed to complete the work for our Mainnet release

Comments

@BlocksOnAChain
Copy link

Description
Cannon has an unspecified requirement for running go binaries compiled with the go-1.22 runtime. This constraint stems from an incompatibility introduced in go-1.23.

The go-1.23 runtime replaces the sys_pipe usage for wait/notify mechanisms in the epoll event loop with a sys_eventfd based implementation. Since sys_eventfd is not implemented or supported in the current cannon implementation running the op-program, or any binary, with go runtimes newer than go-1.22 would trigger an unhandled syscall runtime panic.

Recommendation
Clearly document the go-runtime requirement and ensure sys_eventfd syscall is implemented prior to upgrading the go-runtime of the op-program

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MT cannon - audit findings grouping for audit findings MT cannon - Mainnet relevant issues needed to complete the work for our Mainnet release
Projects
Development

No branches or pull requests

1 participant