We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
illegal operation on a directory, open '.dir/
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.
The text was updated successfully, but these errors were encountered:
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' }
Sorry, something went wrong.
Can you provide a repro case I can access to test?
Any solution or workaround?
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.
No branches or pull requests
Given the following configuration:
The following is returned as an error:
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.
The text was updated successfully, but these errors were encountered: