Skip to content

Reports of debug_standardTraceBadBlockToFile not working #31694

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
Open
s1na opened this issue Apr 22, 2025 · 3 comments
Open

Reports of debug_standardTraceBadBlockToFile not working #31694

s1na opened this issue Apr 22, 2025 · 3 comments
Assignees
@jwasinger
Labels
type:bug

Comments

@s1na
Copy link
Contributor

s1na commented Apr 22, 2025

There have been reports that debug_standardTraceBadBlockToFile writes empty files when used on mainnet. We need to look into this. When an issue happens this method is useful for debugging.
@s1na s1na added the type:bug label Apr 22, 2025
@MariusVanDerWijden
Copy link
Member

Do you have a link or some more info for these reports?

@s1na
Copy link
Contributor Author

s1na commented Apr 24, 2025

This is one of them: https://discord.com/channels/482467812179181568/482467812816977921/1356732097854836807
I faced this myself when debugging the same issue. But you kinda need an archive node to reproduce it or a private network with bad blocks so I can't share much more right now.

@jwasinger
Copy link
Contributor

I'm seeing the same thing standardTraceBlockToFile

@jwasinger jwasinger self-assigned this Apr 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jwasinger jwasinger

Labels
type:bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@s1na @jwasinger @MariusVanDerWijden