You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when running the replayer, Log4j2 outputs Unable to format msg along with java.lang.IllegalArgumentException: found 1 argument placeholders, but provided 0 for pattern
How can one reproduce the bug?
I've created unit tests to simulate the behavior in various instances. Including it here below: As you can see, it happens whenever objects are included in the "setMessage" function, but not when placed in the addArgument.
I'd like to see us pull back the disruptor changes altogether & even just switching to WARN for everything other than progressLogging, tupleLogging, and longRunningActivity logging.
What is the bug?
Currently, when running the replayer, Log4j2 outputs
Unable to format msg
along withjava.lang.IllegalArgumentException: found 1 argument placeholders, but provided 0 for pattern
How can one reproduce the bug?
I've created unit tests to simulate the behavior in various instances. Including it here below: As you can see, it happens whenever objects are included in the "setMessage" function, but not when placed in the addArgument.
What is the expected behavior?
No error message, objects tostring is included in the log without additional parameterization
What is your host/environment?
Java Coretto 11, MacOS M1 Pro Arm64
Do you have any screenshots?
N/A
Do you have any additional context?
N/A
The text was updated successfully, but these errors were encountered: