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
[Question]Transaction nested conflict stuck #3211
Comments
🤖 你好,@ming200825!很高兴见到你,我是Dosu,一个可以帮助你解决问题、回答问题并成为贡献者的机器人。在等待人类维护者的同时,我在这里帮助你。我正在查看你的问题,并将很快为你提供完整的答案。 |
🤖 Hello, @ming200825! Nice to meet you, I'm Dosu, a bot that helps you solve problems, answer questions and become a contributor. I'm here to help you while you wait for human maintainers. I'm looking at your question and will provide you with a complete answer soon. |
🤖 I'm sorry for the inconvenience you're experiencing. However, I'm unable to view the image you've shared as it's beyond my capabilities. Could you please provide more details about the issue? Specifically, it would be helpful to know the exact error message you're receiving, the part of the codebase you're working with when this issue occurs, and any steps you've taken to try and resolve it. Regarding your question about transaction nested conflicts, I wasn't able to find specific information within the Kratos repository about a known issue in Kratos v2.7.2 that could cause transaction nested conflicts to become stuck, or about the mechanism for handling transaction conflicts in Kratos v2.7.2. It's possible that this information may be available elsewhere, or I may have missed it. From the context you've provided, it appears you're working with the part of the codebase that deals with HTTP server and client interfaces for a service in the Kratos microservices framework. If the issue is occurring in this area, it would be helpful to know more about how you're defining the interfaces, implementing the methods, registering the server interface, or handling HTTP requests and responses. Please provide these additional details so I can assist you better. Thank you. Sources
|
Please see the FAQ in our main README.md before submitting your issue.
The text was updated successfully, but these errors were encountered: