Skip to content

Conversation

alarso16
Copy link
Contributor

@alarso16 alarso16 commented Mar 6, 2025

This error log in legacypool.go isn't necessary, since even though the behavior is unexpected, it is handled correctly. A discussion on issue #22301 concluded that this should instead be a warning log.

@fjl fjl changed the title fix(txpool): demote error log to warn core/txpool: demote error log to warn Mar 7, 2025
Copy link
Member

@MariusVanDerWijden MariusVanDerWijden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM

Copy link
Member

@lightclient lightclient left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM

@MariusVanDerWijden MariusVanDerWijden merged commit 49ef375 into ethereum:master Mar 11, 2025
2 checks passed
@MariusVanDerWijden MariusVanDerWijden added this to the 1.15.6 milestone Mar 11, 2025
@alarso16 alarso16 deleted the patch-1 branch March 12, 2025 20:17
GrapeBaBa pushed a commit to optimism-java/shisui that referenced this pull request Mar 16, 2025
This error log in `legacypool.go` isn't necessary, since even though the
behavior is unexpected, it is handled correctly. A discussion on issue
ethereum#22301 concluded that this should instead be a warning log.
sivaratrisrinivas pushed a commit to sivaratrisrinivas/go-ethereum that referenced this pull request Apr 21, 2025
This error log in `legacypool.go` isn't necessary, since even though the
behavior is unexpected, it is handled correctly. A discussion on issue
ethereum#22301 concluded that this should instead be a warning log.
jakub-freebit pushed a commit to fblch/go-ethereum that referenced this pull request Jul 3, 2025
This error log in `legacypool.go` isn't necessary, since even though the
behavior is unexpected, it is handled correctly. A discussion on issue
ethereum#22301 concluded that this should instead be a warning log.
howjmay pushed a commit to iotaledger/go-ethereum that referenced this pull request Aug 27, 2025
This error log in `legacypool.go` isn't necessary, since even though the
behavior is unexpected, it is handled correctly. A discussion on issue
ethereum#22301 concluded that this should instead be a warning log.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants