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

[3.2]Fix:triple protocol echoService invoke. #15127

Merged
merged 2 commits into from
Feb 13, 2025
Merged

Conversation

wuwen5
Copy link
Contributor

@wuwen5 wuwen5 commented Feb 12, 2025

What is the purpose of the change?

The triple protocol encountered an error during echo testing (EchoService)

Exception in thread "main" java.lang.NullPointerException
	at org.apache.dubbo.rpc.protocol.tri.TripleInvoker.isSync(TripleInvoker.java:196)
	at org.apache.dubbo.rpc.protocol.tri.TripleInvoker.doInvoke(TripleInvoker.java:155)

fix #15128

Checklist

  • Make sure there is a GitHub_issue field for the change.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Write necessary unit-test to verify your logic correction. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
  • Make sure gitHub actions can pass. Why the workflow is failing and how to fix it?

@heliang666s
Copy link
Contributor

heliang666s commented Feb 13, 2025

Thanks for your contribution~However, You should run mvn spotless:apply to format before commit your code.@wuwen5

@wuwen5
Copy link
Contributor Author

wuwen5 commented Feb 13, 2025

@heliang666s Done. Thanks!

@wuwen5 wuwen5 changed the title Fix:triple protocol echoService invoke. [3.2]Fix:triple protocol echoService invoke. Feb 13, 2025
@AlbumenJ AlbumenJ merged commit 0c2537c into apache:3.2 Feb 13, 2025
@wuwen5 wuwen5 deleted the 3.2-trip-echo branch February 27, 2025 10:54
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.

3 participants