Skip to content
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

pyln-client: send proper JSONRPC2 errors on failed call #3640

Merged
merged 1 commit into from
Apr 11, 2020

Conversation

darosior
Copy link
Collaborator

@darosior darosior commented Apr 9, 2020

fixes #3638

Added @sr-gi as a co author as he did all the search and found the cause.

@darosior darosior requested a review from cdecker as a code owner April 9, 2020 22:53
@sr-gi
Copy link
Contributor

sr-gi commented Apr 10, 2020

LGTM.

I'd only argue that str may be nicer than repr for the cmd return, since you may want to avoid debugging info on the cmd.

As discussed in #3638, the full traceback is left in the logs anyway, so it may just create nicer returns.

@darosior
Copy link
Collaborator Author

darosior commented Apr 10, 2020 via email

Changelog-Added: pyln now sends proper error on bad calls to plugin methods

Co-Authored-By: Sergi Delgado Segura <sergi.delgado.s@gmail.com>
Copy link
Contributor

@rustyrussell rustyrussell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack ed86321

Good find, thanks!

@rustyrussell rustyrussell merged commit af76bce into ElementsProject:master Apr 11, 2020
@darosior darosior deleted the pyln_nice_error branch April 12, 2020 17:41
sr-gi added a commit to talaia-labs/python-teos that referenced this pull request Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Result for missing required arguments in plugins
3 participants