Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Download to target fails with illegal operation on a directory, open '.dir/ #58

Open
victoryNap opened this issue Jul 15, 2023 · 4 comments

Comments

@victoryNap
Copy link

Given the following configuration:

        name: Download release asset
        uses: dsaltares/fetch-gh-release-asset@master
        with:
          repo: '***'
          version: 'tags/${{ fromJson(steps.get_version.outputs.compiler_version).version }}'
          file: 'test.jar'
          token: ${{ secrets.GHCR_TOKEN }}
          target: '.dir/'

The following is returned as an error:

Run dsaltares/fetch-gh-release-asset@master
  with:
    repo: ***
    version: tags/***
    file: test.jar
    token: ***
    target: .dir/
    regex: false
node:internal/process/promises:27[9](***)
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: EISDIR: illegal operation on a directory, open '.dir/'] {
  errno: -21,
  code: 'EISDIR',
  syscall: 'open',
  path: '.dir/'
}

I know that .dir is available, for the time being, I'm downloading to the workspace root, and moving the jar, but this seems like a bug.

@zischknall
Copy link

got the same error:

node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: EISDIR: illegal operation on a directory, open 'projects/ci'] {
  errno: -21,
  code: 'EISDIR',
  syscall: 'open',
  path: 'projects/ci'
}

@dsaltares
Copy link
Owner

Can you provide a repro case I can access to test?

@Architrixs
Copy link

Any solution or workaround?

@zischknall
Copy link

Hey folks,

I can't really remember this issue.
But I just double checked and it seems I resorted to not use the path input to prevent the issue from happening.

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

No branches or pull requests

4 participants