-
Notifications
You must be signed in to change notification settings - Fork 20.3k
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
Hex number as parameter for start
/count
on engine_getPayloadBodiesByRange
results in error
#26623
Comments
I've made #26624 to address this. The hive test still fails, but now the failure is in the rpc method logic (or the hive test? I haven't looked further). log excerpt from running the test now:
|
Hey @jwasinger, I have not rerun the test myself yet but this looks incorrect because, if we are requesting beyond the latest known block number, it should respond with empty array, instead of null. |
I ran the test using the fix branch and there is something definitely going on:
And we get a block:
Then we request:
Which should return:
|
Unassigned myself. If this is easy for anyone else, feel free to pick it up. I will continue looking into this but I have to do some digging/learning to figure out how to properly debug in Hive. Afaict, the issue is improper serialization of the result from GetPayloadBodiesByRangeV1. |
... well, what does it return? |
doh!
|
System information
Geth version: Geth/v1.11.0-unstable-3a5aceed/linux-amd64/go1.19.5
CL client & version: hive ethereum/hive@97d9b7b
OS & Version: Linux
Commit hash : 3a5acee
Expected behaviour
Sending
QUANTITY
value (see https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md#encoding) asstart
and/orcount
parameters forengine_getPayloadBodiesByRangeV1
(see https://github.com/ethereum/execution-apis/blob/main/src/engine/shanghai.md#request-4) should return a valid response.Actual behaviour
Sending
Results in:
See logs: https://hivetests2.ethdevops.io/suite.html?suiteid=1675704876-3f3a1bd514cc40ba5dfbe08c7a775cb8.json&suitename=engine-withdrawals#test-213
Steps to reproduce the behaviour
Run hive
engine-withdrawals
test suite on latest branch using:The text was updated successfully, but these errors were encountered: