-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
no padding + mcms #16511
no padding + mcms #16511
Conversation
move upgrades to mcms
support extend instruction for solana upgrades
AER Report: CI Coreaer_workflow , commit , Scheduled Run Frequency , Detect Changes , Clean Go Tidy & Generate , test-scripts , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , GolangCI Lint (deployment) , Core Tests (go_core_fuzz) , Core Tests (go_core_race_tests) , lint , SonarQube Scan 1. Transaction simulation failed: [job id where the error happened]Source of Error:
Why: The error indicates that the transaction simulation failed because the program failed to complete. The specific error message "Program BPFLoaderUpgradeab1e11111111111111111111111 not supported by inner instructions" suggests that the program being executed is not supported by the current Solana runtime environment. Suggested fix: Ensure that the program being deployed is compatible with the Solana runtime environment. Verify that all dependencies and configurations are correctly set up and that the program is not using any unsupported instructions. 2. Execution reverted: RBACTimelock: underlying transaction reverted: [job id where the error happened]Source of Error:
Why: The error "execution reverted: RBACTimelock: underlying transaction reverted" indicates that the transaction was reverted by the RBACTimelock contract. This could be due to various reasons such as unregistered node operators, unregistered capabilities, or duplicate signers. Suggested fix: Investigate the specific conditions that caused the RBACTimelock contract to revert the transaction. Ensure that all node operators and capabilities are properly registered and that there are no duplicate signers in the proposal. |
|
Requires
Supports