From 0cedf2477f024e73526315a3433c6e0006e14da0 Mon Sep 17 00:00:00 2001 From: Jim McDonald Date: Fri, 12 Apr 2024 10:59:34 +0100 Subject: [PATCH 1/2] 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. --- apis/node/health.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apis/node/health.yaml b/apis/node/health.yaml index 19f18a8e..1d373ea3 100644 --- a/apis/node/health.yaml +++ b/apis/node/health.yaml @@ -17,7 +17,7 @@ get: "200": description: Node is ready "206": - description: Node is syncing but can serve incomplete data + description: Either the consensus node is syncing, or its execution node is optimistic, so data served may be incorrect "400": description: Invalid syncing status code "503": From 5757bc26fa86338e5c6890f4a2a3b61167f5c6db Mon Sep 17 00:00:00 2001 From: Jim McDonald Date: Fri, 12 Apr 2024 12:04:01 +0100 Subject: [PATCH 2/2] Update apis/node/health.yaml Co-authored-by: Nico Flaig --- apis/node/health.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apis/node/health.yaml b/apis/node/health.yaml index 1d373ea3..0aa363a7 100644 --- a/apis/node/health.yaml +++ b/apis/node/health.yaml @@ -17,7 +17,7 @@ get: "200": description: Node is ready "206": - description: Either the consensus node is syncing, or its execution node is optimistic, so data served may be incorrect + description: Either the beacon node is syncing, or its execution node is optimistic, so data served may be incorrect "400": description: Invalid syncing status code "503":