Don't log JsonParseException in the gateway as errors #9933
Labels
kind/bug
Categorizes an issue or PR as a bug
version:1.3.14
Marks an issue as being completely or in parts released in 1.3.14
version:8.1.0-alpha5
Marks an issue as being completely or in parts released in 8.1.0-alpha5
version:8.1.0
Marks an issue as being completely or in parts released in 8.1.0
Describe the bug
When a user sends a request containing variables (e.g. complete job) and these variables cannot be converted to MsgPack a
JsonParseException
. Currently these exceptions are logged with an error level by the gateway. This is unexpected, as the fault here lies with the user, who sends the wrong variables. We should add an exception to theGrpcErrorMapper#mapErrorToStatus
method so we don't go into the default error logging flow.To Reproduce
{"test":123
Expected behavior
No errors should be logged
Log/Stacktrace
Full Stacktrace
Environment:
The text was updated successfully, but these errors were encountered: