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

Prysm v5.2.0 could not retrieve blocks for slot 11006593: could not snappy decode block: snappy: corrupt input #14891

Open
exp0nge opened this issue Feb 7, 2025 · 1 comment
Open

Prysm v5.2.0 could not retrieve blocks for slot 11006593: could not snappy decode block: snappy: corrupt input #14891

exp0nge opened this issue Feb 7, 2025 · 1 comment
Assignees
@rkapka
Labels
Bug Something isn't working

Comments

@exp0nge
Copy link

exp0nge commented Feb 7, 2025 •
edited
Loading

Describe the bug

It looks like missed slots are not returning 404 but instead 500 with

could not retrieve blocks for slot 11006593: could not snappy decode block: snappy: corrupt input

Has this worked before in a previous version?

🔬 Minimal Reproduction

No response

Error

Platform(s)

No response

What version of Prysm are you running? (Which release)

No response

Anything else relevant (validator index / public key)?

No response
@exp0nge exp0nge added the Bug Something isn't working label Feb 7, 2025
@babakgemini
Copy link

babakgemini commented Feb 7, 2025 •
edited
Loading

also when you try curl -s https://beaconcha.in/api/v1/block/11006594 | jq it doesn't load

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rkapka rkapka

Labels
Bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@exp0nge @rkapka @babakgemini