When calling the send_transaction RPC, the response currently includes the full stack trace when an error occurs. This behavior is not ideal, as the stack trace information is better suited for internal debugging rather than being exposed in RPC responses. Including stack traces in RPC responses can also lead to larger payloads.
Bug Report
When calling the send_transaction RPC, the response currently includes the full stack trace when an error occurs. This behavior is not ideal, as the stack trace information is better suited for internal debugging rather than being exposed in RPC responses. Including stack traces in RPC responses can also lead to larger payloads.
Current Behavior
pretty print the message:
Environment
ckb --version
]uname -a
]Additional context/Screenshots