Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Clarify use of 206 status code for node health. #442

Merged
merged 2 commits into from
Apr 12, 2024
Merged

Clarify use of 206 status code for node health. #442

merged 2 commits into from
Apr 12, 2024

Commits on Apr 12, 2024

  1. Clarify use of 206 status code for node health. 

    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.
    @mcdee
    mcdee committed Apr 12, 2024
    Configuration menu
    Copy the full SHA
    0cedf24 View commit details
    Browse the repository at this point in the history

  2. Update apis/node/health.yaml 

    Co-authored-by: Nico Flaig <[email protected]>
    @mcdee @nflaig
    mcdee and nflaig authored Apr 12, 2024
    Configuration menu
    Copy the full SHA
    5757bc2 View commit details
    Browse the repository at this point in the history