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

After rpc call, error cannot be returned correctly #3169

Closed
smilefisher opened this issue Jan 23, 2024 · 3 comments
Closed

After rpc call, error cannot be returned correctly #3169

smilefisher opened this issue Jan 23, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@smilefisher
Copy link

What happened:

Service A call service B, B return error, bug A can not parse the error
image

What you expected to happen:

B parse the same error

How to reproduce it (as minimally and precisely as possible):

normal use

Anything else we need to know?:

Environment:

  • Kratos version (use kratos -v):
    kratos version v2.7.0
  • Go version (use go version):
    go version go1.20.7 windows/amd64
  • OS (e.g: cat /etc/os-release):
    windows/amd64
  • Others:
@smilefisher smilefisher added the bug Something isn't working label Jan 23, 2024
@smilefisher
Copy link
Author

我想直接返回B服务返回的错误,but B服务无法解析这个错误

@kratos-ci-bot
Copy link
Collaborator

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


I want to directly return the error returned by service B, but service B cannot parse this error.

@smilefisher
Copy link
Author

so i have to did this
image

@smilefisher smilefisher changed the title rpc call lose error rpc Jan 23, 2024
@smilefisher smilefisher changed the title rpc rpc调用后,服务正确的返回错误 Jan 23, 2024
@smilefisher smilefisher changed the title rpc调用后,服务正确的返回错误 After rpc call, error cannot be returned correctly Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants