fix: reconcile auto-increment state for copy and clone - #26197
Dequeued — pull request dequeued
- ✅ Entered queue —
2026-07-28 06:28 UTC· Rule:main· triggered by a@mergifyio queuecommand - 🟠 Checks running · in-place
- 🚫 Left the queue —
2026-07-28 08:23 UTC· atc61c432cc5fb0fe94f0acdc4fcbf1e7258fcc053
This pull request spent 1 hour 55 minutes 42 seconds in the queue, with no time running CI.
Waiting for
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC) -
check-skipped = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC) -
check-success = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone CI / UT Test on Ubuntu/x86 -
check-skipped = Matrixone CI / UT Test on Ubuntu/x86 -
check-success = Matrixone CI / UT Test on Ubuntu/x86
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone CI / SCA Test on Linux/arm64 -
check-skipped = Matrixone CI / SCA Test on Linux/arm64 -
check-success = Matrixone CI / SCA Test on Linux/arm64
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY) -
check-skipped = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY) -
check-success = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY)
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone Utils CI / Coverage -
check-skipped = Matrixone Utils CI / Coverage -
check-success = Matrixone Utils CI / Coverage
-
- any of: [🛡 GitHub branch protection]
-
check-neutral = Matrixone UT Coverage / UT Coverage on Ubuntu/x86 -
check-skipped = Matrixone UT Coverage / UT Coverage on Ubuntu/x86 -
check-success = Matrixone UT Coverage / UT Coverage on Ubuntu/x86
-
All conditions
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC) -
check-skipped = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC) -
check-success = Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC)
-
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone CI / UT Test on Ubuntu/x86 -
check-skipped = Matrixone CI / UT Test on Ubuntu/x86 -
check-success = Matrixone CI / UT Test on Ubuntu/x86
-
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone CI / SCA Test on Linux/arm64 -
check-skipped = Matrixone CI / SCA Test on Linux/arm64 -
check-success = Matrixone CI / SCA Test on Linux/arm64
-
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY) -
check-skipped = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY) -
check-success = Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY)
-
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone Utils CI / Coverage -
check-skipped = Matrixone Utils CI / Coverage -
check-success = Matrixone Utils CI / Coverage
-
- any of [🛡 GitHub branch protection]:
-
check-neutral = Matrixone UT Coverage / UT Coverage on Ubuntu/x86 -
check-skipped = Matrixone UT Coverage / UT Coverage on Ubuntu/x86 -
check-success = Matrixone UT Coverage / UT Coverage on Ubuntu/x86
-
#review-threads-unresolved = 0[🛡 GitHub branch protection]github-review-approved[🛡 GitHub branch protection] (documentation)github-review-decision = APPROVED[🛡 GitHub branch protection] (documentation)
Reason
Pull request #26197 has been dequeued
Pull request from fork cannot be queued. This pull request comes from a fork, and Mergify needs the author's permission to update its branch.
The author needs to enable "Allow edits from maintainers" on this pull request.
Failing checks:
- 🟠 Matrixone CI / SCA Test on Linux/arm64 (job log)
- 🟠 Matrixone CI / UT Test on Ubuntu/x86 (job log)
- 🟠 Matrixone Compose CI / multi cn e2e bvt test docker compose(PROXY) (job log)
- 🟠 Matrixone Standlone CI / e2e BVT Test on Linux/x64(LAUNCH, PESSIMISTIC) (job log)
- 🟠 Matrixone UT Coverage / UT Coverage on Ubuntu/x86 (job log)
Hint
You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.
Tick the box to put this pull request back in the merge queue (same as @mergifyio queue).
- Requeue this pull request