rpc: fix time key collision for logger with json output #24112
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JacekGlen
pushed a commit
to JacekGlen/go-ethereum
that referenced
this pull request
May 26, 2022
The "t" key overrides the log message time in JSON output. Co-authored-by: Felix Lange <fjl@twurst.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's
tparameter overwriting for messages inrpcpackage when Geth node uses--log.jsonflag. Here's an example of such overwriting:{"err":"sealing paused while waiting for transactions","lvl":"warn","msg":"Block sealing failed","t":"2021-12-15T14:16:48.131233613+03:00"} {"lvl":"dbug","msg":"Served rpc_modules","reqid":"1","t":"33.633µs"} {"lvl":"trce","msg":"Handled RPC response","reqid":"1","t":"334ns"} {"lvl":"dbug","msg":"Served web3_clientVersion","reqid":"2","t":"27.963µs"}In this PR I've tried to fix this by renaming
tparameter.