-
Notifications
You must be signed in to change notification settings - Fork 912
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
trace payment_continue and payment mods #7556
trace payment_continue and payment mods #7556
Conversation
Thanks @JssDWt, I've been wanting to instrument this part of the code for quite a while, and never had the muse to get started. I added #7575 on top of your change to instrument all JSON-RPC calls that plugins start, and we can likely also instrument all entrypoints to the plugin as well (rpcmethod, hook and notifications). |
dd941ac
to
c25f23e
Compare
The `send_outreq` function is a good place to suspend and resume traces, since these are usually the places where we hand off control back to the `io_loop`. This assumes that we do not continue doing heavy liftin after we have queued an `outreq` call, but that is most likely the case anyway. This frees us from having to track suspensions whenever we call the RPC from a plugin.
c25f23e
to
e0ce284
Compare
Rebased. And also fixed a bug where the |
Pretty! I missed this on the milestone, fixed now. Rebasing now. |
This is confusing. #7575 says it builds on this, this says it's now based on that. And I can't force push to this branch to rebase. So I'm going to add to the confusion by opening another PR! |
No description provided.