-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Type of error
field in structlog logger differs from geth, alloy
#12085
Comments
tnx. pr: #12089 |
@AlexeyAkhunov seems to be the original committer of those lines so tagging him. Perhaps he knows something I don't about why the line was already there, but commented out ( |
AskAlexSharov
added a commit
that referenced
this issue
Oct 1, 2024
cffls
pushed a commit
to 0xPolygonZero/erigon
that referenced
this issue
Oct 4, 2024
taratorio
pushed a commit
that referenced
this issue
Oct 8, 2024
taratorio
added a commit
that referenced
this issue
Oct 8, 2024
AskAlexSharov
pushed a commit
that referenced
this issue
Oct 16, 2024
yperbasis
pushed a commit
that referenced
this issue
Oct 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
Commit hash: c293883
Expected behaviour
The field
error
should probably be logged as a string to be compatible with Geth, Alloy.Actual behaviour
The field
error
is logged as an object containing a string.Steps to reproduce the behaviour
I don't know of a
tx_id
on a public chain, whose logs contains theerror
field, but here is the command I used to confirm this issue:Source
erigon/eth/tracers/logger/json_stream.go
Lines 128 to 131 in c293883
Suggested fix
The text was updated successfully, but these errors were encountered: