Nick Fields

Encountered this in a yarn (v1.22.18) monorepo where the Prisma schema is in a non-default location. I worked around it by adding a `prepare` (post-install) script to the root package.json:...

Our app requires MacOS and bare metal GPU access, so the docker images are not helpful here. What compounds the issue is Chrome's rolling updates, and how they don't really...

> @haipinglu would you be ok if I raise a PR for this? Perhaps a simple `SHELL.split(' ')[0]` for that switch? Please do!

I don't know if this is configurable? I don't think it is, but if you can find where it's documented to change this default display behavior I'd be happy to...

@ayoubeddafali I'm reluctant to add anything without test(s). Take a look at the other ["integration tests"](https://github.com/nick-fields/retry/blob/master/.github/workflows/ci_cd.yml#L27) and add similar.

Thanks for the contribution! This seems like an easy enough fix. Can you add a few tests to the `CI/CD` [workflow](.github/workflows/ci_cd.yml)? At least two to verify that the traditional multiline...

Thanks for your issue. Can you retest with v2.8.1? I've switched from `exec` to `spawn` and output should be displayed now. ```yaml - name: Retry Step uses: nick-fields/[email protected] ```

FWIW, I started seeing this today in our Netlify builds and once locally. We're using [email protected] (which uses [email protected]) and have been for a few weeks before seeing this for...

The preinstall script wasn't enough for us for some reason. We use yarn, so pinning the version to 2.5.1 via the [resolutions](https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/) feature has worked so far

I'm also seeing this intermittently with 13.4.1 and 13.10.2 when deploying v1 functions. I just today had 6 functions fail to deploy, 2 that said "Waiting to retry", and 1...