Skip to content

merge queue: checking main (a4b93c0) and #647 together#650

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/1ffad0a496
Closed

merge queue: checking main (a4b93c0) and #647 together#650
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/1ffad0a496

Conversation

@mergify

@mergify mergify Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (a4b93c0) and #647 are queued together for merge.

This pull request has been created by Mergify to check the mergeability of #647.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

No extra conditions.

Required conditions to stay in the queue:

---
checking_base_sha: a4b93c0e6393ed480249ba2848135d71bb1ed2a9
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 647
    scopes: []
scopes: []
...

Zo Bot and others added 2 commits June 30, 2026 11:28
…exError

Calling wait_chain() with no strategies stored an empty tuple in
self.strategies. The first call to __call__ then evaluated
min(max(1, 1), 0) == 0, so self.strategies[wait_func_no - 1]
turned into self.strategies[-1] and raised IndexError, which is
opaque for what is really a programmer error at construction time.

Validate in __init__ and raise ValueError('wait_chain() requires
at least one strategy') so the failure happens at the point where
the bad configuration is created, not later when the wait function
is first evaluated inside a running retry.
@mergify mergify Bot closed this Jul 3, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/1ffad0a496 branch July 3, 2026 08:05
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.

0 participants