-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPC send_transaction
should not include stack trace in the RPC response
#4698
Comments
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Nov 26, 2024
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Nov 26, 2024
Signed-off-by: Eval EXEC <[email protected]>
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Nov 26, 2024
Signed-off-by: Eval EXEC <[email protected]>
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Nov 26, 2024
Signed-off-by: Eval EXEC <[email protected]>
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Nov 26, 2024
Signed-off-by: Eval EXEC <[email protected]>
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Nov 26, 2024
Signed-off-by: Eval EXEC <[email protected]>
eval-exec
added a commit
to eval-exec/ckb
that referenced
this issue
Nov 26, 2024
Signed-off-by: Eval EXEC <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: