Skip to content

Downgrade ERROR to something less less terrifying? #5794

@brsq

Description

@brsq

A pretty frequent source of confusion is the "errors" that appear in debug.log that really shouldn't be, is there any reason that these shouldn't be changed to warnings or just informational prints? "Error" just comes on a bit too strong for my liking and doesn't really reflect what the log print is talking about (rejected transaction, not someone hitting the self destruct button).

Propose:

ERROR: AcceptToMemoryPool : non-final

Becomes:

INFO: AcceptToMemoryPool : non-final

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions