-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
test: update beacon api spec version to 2.4.1 #5695
Conversation
Performance Report✔️ no performance regression detected Full benchmark results
|
ff9b022
to
944f486
Compare
Having a jumbo PR bundling all 2.4.1 items is too much, implement an explicit ignore list and go one be one |
This PR should just be used to keep track of missing items and test against latest spec version, in the end can close it or just merge the spec version update.
Was thinking about that as well, but there is still the issue that some APIs need new parameters for spec tests to pass. |
To track progress it's best to use issues. This PR seems it will be open for a long time so just best to reference the branch on the issue if it has value. |
Generally agree, but we can check spec compliance programmatically in this case which is not possible if an issue is used. Would have just rebased this branch against unstable after there has been progress on the APIs to get updated results as it will not be possible to update spec tests to 2.4.1 on unstable for a while. If this branch gets stale or unused after a while if there is no progress we should close it. Feel free to close is now already if you feel strongly about using an issue instead, will create the according issue then to keep track. |
Yes please open the issue, I'm just trying to keep our list of open PRs under control 🙏 To programatically test that a branch passes tests you can trigger a manual workflow lodestar/.github/workflows/test.yml Line 13 in 6638ea7
|
Motivation
Compliance to latest beacon api spec (v2.4.1)
Description
This branch is used to test our API against latest beacon api spec.
There are several updates required
finalized
property to HTTP API responses #5693el_offline
ineth/v1/node/syncing
#5542syncing_status
query parameter to health API #5702