-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
saga mode replay context lost start, issue 5682 reopen !! #6257
Comments
@wt-better Please help with this question |
What version of seata-client are you using? |
this issue have fixed on 1.8, but not 2.x, I will fixed it on 2.x later. |
@wt-better I suggest including it in the milestone for version 2.1.0. |
@wt-better Is there any progress information here ? |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ⅰ. Issue Description
reopen!
Ⅱ. Describe what happened
https://github.com/apache/incubator-seata/blob/2.x/saga/seata-saga-engine/src/main/java/io/seata/saga/engine/impl/ProcessCtrlStateMachineEngine.java
Ⅲ. Describe what you expected to happen
https://github.com/apache/incubator-seata/blob/1.8.0/saga/seata-saga-engine/src/main/java/io/seata/saga/engine/impl/ProcessCtrlStateMachineEngine.java
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
The text was updated successfully, but these errors were encountered: