Skip to content

Conversation

@arnetheduck
Copy link
Member

@arnetheduck arnetheduck commented Nov 21, 2025

Although it has no practical impact on the processor (except if
addBlock were cancelled, which it never is), the acquire should be
outside the finally (since obvisouly, if it were cancelled it will not
be acquired and therefore shouldn't be released)

Although it has no practical impact on the processor (except if
`addBlock` were cancelled, which it never is), the `acquire` should be
outside the `finally` (since obvisouly, if it were cancelled it will not
be acquired and therefore shouldn't be released)
@arnetheduck arnetheduck changed the title Move lock fix late acquire Nov 21, 2025
@github-actions
Copy link

Unit Test Results

       12 files  ±0    2 432 suites  ±0   47m 11s ⏱️ -44s
12 657 tests ±0  12 092 ✔️ ±0  565 💤 ±0  0 ±0 
63 632 runs  ±0  62 904 ✔️ ±0  728 💤 ±0  0 ±0 

Results for commit e22897b. ± Comparison against base commit 688b3ee.

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.

1 participant