Yicong-Huang opened a new issue, #4617: URL: https://github.com/apache/texera/issues/4617
### Task Summary The `Direct Backport Push` workflow (`.github/workflows/direct-backport-push.yml`) sometimes finds zero backport targets immediately after a merge to `main`, and the `push-backports` job is skipped. Re-running the workflow a minute later succeeds. Example: run [25233602734 attempt 1](https://github.com/apache/texera/actions/runs/25233602734) for the merge of #4600 (which had a `release/v1.1.0-incubating` label) logged: ``` No merged pull request is associated with 11d475a2d7406d012a95dd6909c53a13156ef5f5. ``` Root cause: the `Resolve merged PR and green targets` step calls `GET /repos/{owner}/{repo}/commits/{commit_sha}/pulls`, which depends on GitHub's commit↔PR association index. That index is rebuilt asynchronously after a squash merge and can return empty for several seconds, while the `push` event fires immediately. Attempt 2 (a minute later) returned the PR and worked. ### Proposed fix Make PR resolution robust to this lag, in priority order: 1. **First, parse the squash-merge commit message.** ASF squash merges produce a first line ending with `(#NNNN)`. Regex-extract that PR number — it's deterministic and doesn't depend on any async index. 2. **If the message doesn't match (manual merge, weird commit), fall back to the API with retries.** At least 5 attempts on `commits/{sha}/pulls`, with exponential backoff (e.g., 2s, 4s, 8s, 16s, 32s) before giving up. ### Priority P2 – Medium ### Task Type - [x] DevOps / Deployment -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
