Fix Plan

To resolve the issue, we need to ensure that the third_party/cutlass directory is properly initialized by running /usr/bin/git submodule sync --recursive before attempting to import Cutlass.

Here are the concrete steps:

• Add the following command to the CI workflow before the try_import_cutlass step:

  - name: Sync submodules
    run: /usr/bin/git submodule sync --recursive

• Alternatively, you can also use the following command to initialize and update the submodules:

  - name: Init and update submodules
    run: |
      git submodule init
      git submodule update --recursive

• Verify that the third_party/cutlass directory is properly initialized after running the above commands.

Verification

To verify that the fix worked, check the CI job logs to ensure that the third_party/cutlass directory is initialized and the try_import_cutlass step succeeds.

Extra Tips

• Make sure to test the changes in a non-production environment before deploying them to production.
• Consider adding a check to ensure that the third_party/cutlass directory is properly initialized before attempting to import Cutlass, to prevent similar issues in the future.