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.

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

Erroneous warning in logs #8562

Closed
mcdee opened this issue Sep 4, 2024 · 1 comment · Fixed by #8574
Closed

Erroneous warning in logs #8562

mcdee opened this issue Sep 4, 2024 · 1 comment · Fixed by #8574
Assignees
Labels
bug 🐞 Something isn't working

Comments

@mcdee
Copy link
Contributor

mcdee commented Sep 4, 2024

Description

teku is generating warnings when blocks are requested via the v3 endpoint that appear to be erroneous.

Steps to Reproduce (Bug)

Request a block via the v3 endpoint https://ethereum.github.io/beacon-APIs/#/Validator/produceBlockV3

Check the logs, e.g.:

2024-09-04 11:45:13.001 INFO  - Creating unsigned block for slot 2462326
2024-09-04 11:45:13.850 WARN  - Builder endpoint is available but a non-blinded block has been requested

It appears that this warning will always be generated for the v3 endpoint as by the specification of this call teku will always fetch both blinded and non-blinded payloads to compare values. The warning should not be generated for a call to the v3 endpoint.

Versions (Add all that apply)

teku --version
teku/v24.8.0/linux-x86_64/-ubuntu-openjdk64bitservervm-java-21
@rolfyone rolfyone added the bug 🐞 Something isn't working label Sep 5, 2024
@rolfyone rolfyone self-assigned this Sep 5, 2024
@rolfyone
Copy link
Contributor

rolfyone commented Sep 5, 2024

Hey - thanks - seems like a quick win. I'll clean that up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐞 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants