BUG: recover_sub_pool no longer raises on concurrent create_actor - #204
Merged
qinxuye merged 3 commits intoAug 30, 2026
Merged
Mergify / Summary
succeeded
Aug 30, 2026 in 0s
2 potential rules
Rule: automatic update (update)
-
#commits-behind > 0[📌 update requirement] -
-closed[📌 update requirement] -
-conflict -
-conflict[📌 update requirement] -
-draft -
queue-position = -1[📌 update requirement]
Rule: Automatic merge (merge)
-
#approved-reviews-by>=2 -
-closed[📌 merge requirement] -
check-success=build_test_job (macos-13, 3.11, xoscar) -
check-success=build_test_job (macos-13, 3.8, xoscar) -
check-success=build_test_job (ubuntu-latest, 3.8, xoscar) -
check-success=build_test_job (windows-latest, 3.11, xoscar) -
check-success=build_test_job (windows-latest, 3.8, xoscar) -
check-success=codecov/project -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] -
base=main -
check-success=build_test_job (ubuntu-latest, 3.10, xoscar) -
check-success=build_test_job (ubuntu-latest, 3.11, xoscar) -
check-success=build_test_job (ubuntu-latest, 3.9, xoscar) -
check-success=lint (ubuntu-latest, 3.10) -
github-review-approved[🛡 GitHub branch protection] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branch
Additionally, on Mergify dashboard you can:
- look at your merge queues
- generate the Mergify configuration with the config editor.
Finally, you can contact us on https://mergify.com
Loading