search

AkhileshNS / heroku-deploy

A simple github action that dynamically deploys an app to heroku
MIT License
974 stars 254 forks source link

Error: spawnSync /bin/sh ENOBUFS #82

Open jdarnok opened 3 years ago

jdarnok commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

@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 commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

I also keep getting this error.

Run akhileshns/heroku-deploy@v3.12.12
  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.