[Copilot]

The Clone commit and package Actions job regressed after switching code_sync.yml to actions/checkout recursive submodule fetching. On the HongKong clone runner, submodule checkout failed during external fetches (zlib, cccl), causing the packaging stage to never run.

• Root cause

  • actions/checkout with submodules: recursive pushed all submodule cloning through checkout's built-in path, which proved fragile on this runner/network path.
  • The first hard failure in the logs was during submodule fetch, with transfer errors such as curl 28, early EOF, and invalid index-pack output.

• Workflow change

  • Remove submodules: recursive from the initial checkout in .github/workflows/code_sync.yml.
  • Add a dedicated submodule sync/update step after checkout so the job still packages a repo with populated submodules.

• Retry behavior

  • Follow the same recovery pattern already used in Paddle CI:
    • git submodule sync --recursive
    • git submodule update --init --force --recursive --depth 1
    • on failure: git submodule deinit -f --all, clear .git/modules, then retry once

• Fail-fast hardening

  • Add set -euo pipefail to the retry step so a failed retry cannot fall through to tarball packaging with incomplete submodules.

- name: Sync submodules with retry
  working-directory: Paddle
  run: |
    set -euo pipefail
    git submodule sync --recursive
    if ! git submodule update --init --force --recursive --depth 1; then
      git submodule deinit -f --all || true
      rm -rf .git/modules
      git submodule sync --recursive
      git submodule update --init --force --recursive --depth 1
    fi

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}