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

✨ Update logging of closed RPC errors #623

Merged

Conversation

abrugaro
Copy link
Contributor

Solves #500

@abrugaro abrugaro changed the title ✨ Update logging of closed RPC errors :sparkles; Update logging of closed RPC errors Jun 19, 2024
@abrugaro abrugaro changed the title :sparkles; Update logging of closed RPC errors ✨ Update logging of closed RPC errors Jun 19, 2024
@jmle jmle requested a review from shawn-hurley June 19, 2024 14:24
@abrugaro abrugaro force-pushed the update-rpc-closed-error-reporting branch 2 times, most recently from b56144b to 0e649cc Compare June 21, 2024 11:38
Signed-off-by: Alejandro Brugarolas <abrugaro@redhat.com>
@abrugaro abrugaro force-pushed the update-rpc-closed-error-reporting branch from 0e649cc to 63a54f1 Compare June 21, 2024 11:51
@shawn-hurley
Copy link
Contributor

I love the error method big +1 on that.

I wonder if we can add this at the end of the Call and Notify calls in the jsontrpc2_v2 package here:

I am thinking something in the Call and Notify calls here: https://github.com/konveyor/analyzer-lsp/blob/main/jsonrpc2_v2/conn.go#L312

This would allow for other providers to get the benefit if they are using these packages as well?

@jmle jmle self-requested a review June 25, 2024 09:20
@abrugaro
Copy link
Contributor Author

abrugaro commented Jul 1, 2024

Thanks for your comment @shawn-hurley

In the call method, should I add it here: https://github.com/konveyor/analyzer-lsp/blob/main/jsonrpc2_v2/conn.go#L354 ? and here for Notify: https://github.com/konveyor/analyzer-lsp/blob/main/jsonrpc2_v2/conn.go#L288?

And one more question, should I do the same for the jsonrpc2 (v1) package?

Thanks!!

@shawn-hurley
Copy link
Contributor

Yes those locations look correct to me

and yes if you can add it in v1 as well that would be amazing

Signed-off-by: Alejandro Brugarolas <abrugaro@redhat.com>
@abrugaro abrugaro force-pushed the update-rpc-closed-error-reporting branch from f8c55e2 to f096ee5 Compare July 4, 2024 13:56
@shawn-hurley
Copy link
Contributor

@abrugaro, we are experiencing some issues with the CI system, so while this is a low-risk change that I would normally merge on green, this might take a little longer to get in. I am sorry

@abrugaro
Copy link
Contributor Author

abrugaro commented Jul 5, 2024

@abrugaro, we are experiencing some issues with the CI system, so while this is a low-risk change that I would normally merge on green, this might take a little longer to get in. I am sorry

Sure, its my first contribution to this project so I prefer to wait to be sure that everything is ok before merging 😄

@shawn-hurley shawn-hurley merged commit 57a736a into konveyor:main Jul 12, 2024
6 checks passed
@shawn-hurley
Copy link
Contributor

Thank you @abrugaro this is a really helpful change!

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.

2 participants