You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
time="2024-06-08 20:13:34" level=info msg="Syncing with beacon node to align on chain genesis info" prefix=client
time="2024-06-08 20:13:34" level=warning msg="Could not determine if beacon chain started" error="could not receive ChainStart from stream: failed to get genesis data: genesis data is nil: could not connect" prefix=client
it compares the whole header against the media type but in reality, the conten type header can also include the charset and boundry (see Content-Type#directives).
Lodestar returns the following header
content-type: application/json; charset=utf-8
which is a valid content-type header format, on Prysm side you probably wanna apply something like
I can also confirm that #14075 works as expected, we can enable ssz-only mode on Lodestar with Prysm without any errors (as it falls back to JSON as expected now).
Just a quick side note, I noticed another issue that Prysm VC sends an empty statuses array when calling POST /eth/v1/beacon/states/head/validators. I would argue this is inline with the spec and I improved the handling on Lodestar side (ChainSafe/lodestar#6876) but previously this would just result in returning no validators (irrespective of ids passed).
Describe the bug
Was looking into ChainSafe/lodestar#6633 compatibility issue of Lodestar BN <> Prsym VC.
The error on the Prysm side
But the response from Lodestar looks correct
I believe the reason why the data is
nil
is due to the way the content-type header is checkedprysm/validator/client/beacon-api/json_rest_handler.go
Line 112 in 8413660
it compares the whole header against the media type but in reality, the conten type header can also include the charset and boundry (see Content-Type#directives).
Lodestar returns the following header
which is a valid content-type header format, on Prysm side you probably wanna apply something like
Has this worked before in a previous version?
No response
🔬 Minimal Reproduction
Kurtosis config
Error
No response
Platform(s)
Linux (x86)
What version of Prysm are you running? (Which release)
v5.0.3
Anything else relevant (validator index / public key)?
Related issue ChainSafe/lodestar#6633
The text was updated successfully, but these errors were encountered: