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

Wrong block performance when builder doesn't reveal the block but publishes it #8841

Closed
tbenr opened this issue Nov 21, 2024 · 0 comments · Fixed by #8855
Closed

Wrong block performance when builder doesn't reveal the block but publishes it #8841

tbenr opened this issue Nov 21, 2024 · 0 comments · Fixed by #8855
Assignees
@StefanBratanov

Comments

@tbenr
Copy link
Contributor

tbenr commented Nov 21, 2024

when we publish and relay API timeouts we and up in this situation

2024-11-21 09:03:17.874 | Slow Block Publishing *** Slot: 3022816 start 2639ms, builder_get_payload +3002ms, complete +0ms total: 3002ms 
2024-11-21 09:03:18.877 | Validator   *** Published sync_signature     Count: 5, Slot: 3022816, Root: 54721197c06f2a585f35be1167cd4c5e0d82d024ced02bd52b60049df219c254 |  
2024-11-21 09:03:18.877 | Validator   *** Failed to produce block  Slot: 3022816 Validator: 902afe8

Block performance: epoch 94463, expected 1, produced 0, included 0 (0%)

but the block was actually produced but published by the relay
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@StefanBratanov StefanBratanov

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Track produced block when builder doesn't reveal the payload StefanBratanov/teku
2 participants
@StefanBratanov @tbenr