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

Error: write ENOBUFS on uploading a large file #499

Open
valdearg opened this issue Aug 20, 2024 · 3 comments
Open

Error: write ENOBUFS on uploading a large file #499

valdearg opened this issue Aug 20, 2024 · 3 comments

Comments

@valdearg
Copy link

valdearg commented Aug 20, 2024

I've been using this action for quite a while to make releases, as part of the releases we upload a series of files to the release.

This creates the release and uploads four of the five files, it failed on the much larger file however.

👩‍🏭 Creating new GitHub release for tag 20240820121111.7.10.08.20...
⬆️ Uploading 1.zip...
⬆️ Uploading 2.zip...
⬆️ Uploading 3.zip...
⬆️ Uploading 4.zip...
⬆️ Uploading 5.zip...
Error: write ENOBUFS

I don't know the exact file size of the file however it will be about 1.5GB or 1573321116 bytes.

I've tried the v2 release and the latest release v2.0.

I'm using the following in the YML

      - name: Release
        uses: softprops/action-gh-release@v1
        with:
          tag_name: ${{ env.VERSION_DATE }}.${{ env.VERSION }}
          name: Release ${{ env.PROJECT_NAME }} ${{ env.GITHUB_REF_NAME }} ${{ env.VERSION }} (${{ env.SHORT_SHA }})
          files: | 
            ${{ env.PROJECT_NAME }}*.zip
            4.zip
            5.zip

EDIT: The v1 version is because I'm testing multiple versions at the moment.

@valdearg
Copy link
Author

Using v1 tag results in a successful upload, Wondering if there's a difference in how either the newer versions upload, or if it's a new nodejs version issue?

@cooldark
Copy link

cooldark commented Sep 3, 2024

Got the same error on a windows runner. File size is 1156 MB which is within the GitHub limit of max. 2GB.

Tried setting the parameters in a step before calling the github action but with no luck:
$env:NODE_OPTIONS = "--max-old-space-size=4096"
$env:NODE_OPTIONS >> $PROFILE.AllUsersCurrentHost

@akaszynski
Copy link

I'm running into the same issue on a ubuntu-latest after upgrading to v2. GitHub reports on my release step:

Received request to deprovision: The request was cancelled by the remote provider.

About 7 artifacts each 300-520 MB, for a total of 3.5 GB.

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

3 participants