-
Notifications
You must be signed in to change notification settings - Fork 573
fix(rpc): eth_simulateV1 method handler crash #1955
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
fix(rpc): eth_simulateV1 method handler crash #1955
Conversation
|
Hey @ChanHongMing, I think one or few unit tests are failing, could you check and fix them? |
|
Hello @kamuikatsurgi I have fixed the unit test and it is now working. |
Thanks! We'll get one more approval and merge this PR, thanks for contributing. |
|
hello @kamuikatsurgi , since v2.5.6 release have been made and the target branch of the merge request is v2.5.6-candidate, should I recreate this merge request towards some other branch? |
Hey @ChanHongMing, could you please change the base branch to 'develop' and also pull the latest changes from the 'develop' branch? We will get reviews on this soon and get merged. Thanks! |
|


Description
Fixing the method handler crash issue when calling eth_simulateV1 method.
Changes
Bugfix (non-breaking change that solves an issue)
Breaking changes
Please complete this section if any breaking changes have been made, otherwise delete it
Nodes audience
In case this PR includes changes that must be applied only to a subset of nodes, please specify how you handled it (e.g. by adding a flag with a default value...)
Checklist
Cross repository changes
Testing
Manual tests
Please complete this section with the steps you performed if you ran manual tests for this functionality, otherwise delete it
Additional comments
issue of the eth_simulateV1 is casued by BlobScheduleConfig being nil during calling to CalcBlobFee on Bor chains. After resolving this issue. Calling eth_simulateV1 result in "unexpected withdrawals" error, which indicate withdrawals are not supported in the block body. Then, this issue is resolved by setting it to Nil for bor chain. Finally, functions SetStateSync and SubscribeStateSyncEvent are added to simChainHeadReader so that it implements core.BorStateSyncer