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: spawnSync /bin/sh ENOBUFS #82

Open
jdarnok opened this issue Mar 17, 2021 · 6 comments
Open

Error: spawnSync /bin/sh ENOBUFS #82

jdarnok opened this issue Mar 17, 2021 · 6 comments

Comments

@jdarnok
Copy link

jdarnok commented Mar 17, 2021

Hello, I'm trying to run new version, but I'm getting this error. When I rolledbacked to 3.11, it's still the same. It just worked on a way older version. I'm not entirely sure if this is github-actions/heroku related, but I wanted to ask here first

image

@LVMVRQUXL
Copy link

LVMVRQUXL commented Apr 1, 2021

Hello! I'm getting the same error on v3.12.12.
I tried to rollback to v3.8.9, but it's still the same.

image

@jdarnok
Copy link
Author

jdarnok commented Apr 1, 2021

@LVMVRQUXL Hey. My problem was with current directory option,. Just remove that and use something like that. If you dont use that option, I can't help you 😄
https://elements.heroku.com/buildpacks/ramondonnell/heroku-buildpack-directories

@LVMVRQUXL
Copy link

@LVMVRQUXL Hey. My problem was with current directory option,. Just remove that and use something like that. If you dont use that option, I can't help you 😄
https://elements.heroku.com/buildpacks/ramondonnell/heroku-buildpack-directories

Hey @jdarnok ! Thank you for your help, but I'm trying to release it using docker through this action. 😅
It was working using this action in all my projects, but now it is not working because of this same error...

@sshaw
Copy link

sshaw commented Dec 9, 2021

I had a similar issue due to git failure. execSync will throw an error if the process exists non-zero. It would be great to wrap execSync with try/catch and output the underlying error message.

I can open a PR if you're interested.

@sshaw
Copy link

sshaw commented Dec 9, 2021

Nevermind. I see that is being done and the issue is there's too much output, hence ENOBUFS. Maybe alternate spawning should be used to capture stderr?

@Vrezerino
Copy link

Vrezerino commented Jan 3, 2022

I also keep getting this error.

Run akhileshns/[email protected]
  with:
    heroku_app_name: <redacted>
    heroku_email: <redacted>
    healthcheck:<redacted>
    checkstring: pong
    procfile: web: node index.ts
    rollbackonhealthcheckfailed: true
    branch: HEAD
    dontuseforce: false
    dontautocreate: false
    usedocker: false
    docker_heroku_process_type: web
    delay: 0
    justlogin: false
  env:
    CI: 1
    CYPRESS_CACHE_FOLDER: /home/runner/.cache/Cypress
    npm_config_cache: /home/runner/.npm
    TERM: xterm
Error: Error: spawnSync /bin/sh ENOBUFS

I wasn't sure whether it had something to do with heroku-deploy or the cypress-io action that I use before deploying, seeing as what the output is.

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