-
-
Notifications
You must be signed in to change notification settings - Fork 372
chore: update 404 block/state error messages to match spec examples #7775
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
Merged
+4
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wemeetagain
approved these changes
Apr 30, 2025
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## unstable #7775 +/- ##
============================================
- Coverage 56.04% 56.04% -0.01%
============================================
Files 823 823
Lines 57892 57892
Branches 4452 4451 -1
============================================
- Hits 32448 32445 -3
- Misses 25376 25379 +3
Partials 68 68 🚀 New features to boost your workflow:
|
KaloyanTanev
approved these changes
Apr 30, 2025
Performance Report✔️ no performance regression detected Full benchmark results
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Obol currently uses the message to determine if block was missed for slot and assumes that clients use the same format as per spec example. While I don't think this is a great approach it's simple enough for us to adjust and doesn't hurt to be closer to spec examples.
And the problem with just using the status code (404) right now is that it can either mean "route not implemented" or "block not found", I guess could consider to standardize error codes for this on the beacon-api spec but likely not worth it due to limited use cases, usually status code is good enough.
Description
Update 404 block/state error messages to match spec examples (state 404 message, block 404 message)