Clarify use of 206 status code for node health. #442
Merged
Conversation
This file contains 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
The 206 return code for the node health endpoint does not take into account the situation where the consensus node may be synced by the execution node is optimistic. Clarify that this situation should return the 206 status code.
nisdas
approved these changes
Apr 12, 2024
nflaig
reviewed
Apr 12, 2024
Co-authored-by: Nico Flaig <[email protected]>
nflaig
approved these changes
Apr 12, 2024
rkapka
approved these changes
Apr 12, 2024
This was referenced Jun 29, 2024
Merged
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.
The 206 return code for the node health endpoint does not take into account the situation where the consensus node may be synced by the execution node is optimistic. Clarify that this situation should return the 206 status code.