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

bugfix: the problem of accidentally releasing the global lock #4177

Merged
merged 3 commits into from
Dec 8, 2021

Conversation

funky-eyes
Copy link
Contributor

  • I have registered the PR changes.

Ⅰ. Describe what this PR did

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

@codecov-commenter
Copy link

codecov-commenter commented Dec 7, 2021

Codecov Report

Merging #4177 (e5874f0) into develop (235a053) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##             develop    #4177   +/-   ##
==========================================
  Coverage      49.37%   49.37%           
- Complexity      3764     3765    +1     
==========================================
  Files            700      700           
  Lines          23664    23664           
  Branches        2926     2924    -2     
==========================================
  Hits           11685    11685           
  Misses         10780    10780           
  Partials        1199     1199           
Impacted Files Coverage Δ
.../java/io/seata/server/coordinator/DefaultCore.java 51.70% <100.00%> (ø)

Copy link
Member

@slievrly slievrly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@slievrly slievrly merged commit a3f8dce into apache:develop Dec 8, 2021
@wangliang181230 wangliang181230 added this to the 1.5.0 milestone Dec 17, 2021
@Bughue
Copy link
Contributor

Bughue commented Feb 16, 2022

虽然看代码里rollback是不用释放锁的,但他也在判断status=begin之前进行了globalSession.close()。是不是也改成和commit一样先判断再操作好点?以后这部分逻辑如果变更复杂的话不知道会不会有问题?

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.

None yet

5 participants