Error unknown blob during the execution

[giuliolastra]

Hello,
thanks in advance for support, I'm quite new of github actions and I was trying to archieve a simple checkout of my private repo, in order to copy to a VPS.
I archieved it about 10 days ago, using your php-actions/composer@v5 but today, when I tried to run the actions (after adding just a few lines in my project) I had a totally different execution of your action that ended with this:

unknown blob
Error: Process completed with exit code 1.

I tried also to rollback commit and running same execution but no luck.

How can I solve?

Thanks!

[g105b]

Hi, can you share anything like the configuration yml of your repository so I can take a look?

[giuliolastra]

Sure, here's the first part of my action.

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout Project
      uses: actions/checkout@v2.3.4
      with:
        path: ./
        ref: ${{ github.event.inputs.branch }}
    - name: Checking files
      run: ls -lA
    - name: Composer Install
      uses: php-actions/composer@v5
      with:
        php_version: 7.4
        progress: yes
        dev: no

While on the error I had:

1019b4d6a141: Layer already exists
86d905c1f58e: Layer already exists
22573737ba76: Layer already exists
777b2c648970: Layer already exists
unknown blob
Error: Process completed with exit code 1.

By the way I've runned it now, and the execution was the composer's standard one, ending with a success. But I changed absolutely nothing.

[g105b]

I'm not 100% sure what has caused this, but it sounds like for some reason the Github package repository was not allowing your test runner to pull the package correctly.

Can I confirm that your actions are running successfully again now?

[giuliolastra]

I can confirm that now is working.

it sounds like for some reason the Github package repository was not allowing your test runner to pull the package correctly.

Is there anything that I can do to check this?

Thanks for support!

[g105b]

The only thing I can think of to debug this is to run the docker commands yourself locally, but that's a bit farfetched, and Github Actions are quite opaque with their debuggability... for now, let's hope the issue doesn't crop up again. Please let me know if you have any other issues with the action.

Cheers.