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

fix: pin bahmutov/npm-install version #3587

Closed

Conversation

jenseng
Copy link
Contributor

@jenseng jenseng commented Jun 28, 2022

v1.8.16 breaks cache miss installs on windows, which blocks any PRs/commits that change dependencies. Opened this issue to address the underlying bug, but in the meantime we can pin to the prior version to get things working again.

Making this PR against main instead dev, since the jobs explicitly use remix-run/remix/.github/workflows/reusable-test.yml@main, but I can switch it up if y'all like. Just trying to get my 4-month-old PR unblocked yet again 😆😭

Additional context:

Testing Strategy:

  • Validated that v1.8.15 fixes cache miss installs on windows here

@jenseng
Copy link
Contributor Author

jenseng commented Jun 28, 2022

Hmm maybe we should just remove this step altogether and instead call yarn install --frozen-lockfile ... we're already doing dependency caching via actions/setup-node@v3:

        uses: actions/setup-node@v3
        with:
          node-version-file: ".nvmrc"
          cache: "yarn"

@kentcdodds I see bahmutov/npm-install@v1 was added here... is there something that it gives us on top of what actions/setup-node@v3 already provides?

@jenseng
Copy link
Contributor Author

jenseng commented Jun 28, 2022

Yeah based on my testing, actions/setup-node@v3' caching already does everything we need. bahmutov/npm-install@v1 just slows down and breaks the build, so we should just remove it :)

jenseng added a commit to jenseng/remix that referenced this pull request Jun 28, 2022
We already use `actions/setup-node@v3` which has equivalent caching
functionality that isn't broken for yarn+windows (or yarn 2+ across the
board). So just use that wherever possible. In addition to fixing builds,
this has the added benefit of slightly speeding them up, since we won't
double-cache things (in some cases we had both caches enabled).

For context, see bahmutov/npm-install#146, in
particular [this comment](bahmutov/npm-install#146 (comment)) and linked test output.

This is an alternative to remix-run#3587 or otherwise waiting for `bahmutov/npm-install`
to get fixed.
jenseng added a commit to jenseng/remix that referenced this pull request Jun 28, 2022
We already use `actions/setup-node@v3` which has equivalent caching
functionality that isn't broken for yarn+windows (or yarn 2+ across the
board). So just use that wherever possible. In addition to fixing builds,
this has the added benefit of slightly speeding them up, since we won't
double-cache things (in some cases we had both caches enabled).

Making this PR against `main` instead `dev`, since the jobs explicitly
use `remix-run/remix/.github/workflows/reusable-test.yml@main`, but I can
switch it up if y'all like. Just trying to get my 4-month-old PR unblocked
yet again 😆😭

For context, see bahmutov/npm-install#146, in
particular [this comment](bahmutov/npm-install#146 (comment)) and linked test output.

This is an alternative to remix-run#3587 or otherwise waiting for `bahmutov/npm-install`
to get fixed.
jenseng added a commit to jenseng/remix that referenced this pull request Jun 28, 2022
We already use `actions/setup-node@v3` which has equivalent caching
functionality that isn't broken for yarn+windows (or yarn 2+ across the
board). So just use that wherever possible. In addition to fixing builds,
this has the added benefit of slightly speeding them up, since we won't
double-cache things (in some cases we had both caches enabled).

Making this PR against `main` instead `dev`, since the jobs explicitly
use `remix-run/remix/.github/workflows/reusable-test.yml@main`, but I can
switch it up if y'all like. Just trying to get my 4-month-old PR unblocked
yet again 😆😭

For context, see bahmutov/npm-install#146, in
particular [this comment](bahmutov/npm-install#146 (comment)) and linked test output.

This is an alternative to remix-run#3587 or otherwise waiting for `bahmutov/npm-install`
to get fixed.
@jenseng jenseng force-pushed the pin-npm-install-workflow-step branch from 37abb25 to 9716a58 Compare June 28, 2022 22:08
@jenseng
Copy link
Contributor Author

jenseng commented Jun 28, 2022

Alternative PR, just remove it altogether where we can: #3593

@jenseng jenseng marked this pull request as draft June 28, 2022 22:39
jenseng added a commit to jenseng/remix that referenced this pull request Jun 28, 2022
We already use `actions/setup-node@v3` which has equivalent caching
functionality that isn't broken for yarn+windows (or yarn 2+ across the
board). So just use that wherever possible. In addition to fixing builds,
this has the added benefit of slightly speeding them up, since we won't
double-cache things (in some cases we had both caches enabled).

Making this PR against `main` instead `dev`, since the jobs explicitly
use `remix-run/remix/.github/workflows/reusable-test.yml@main`, but I can
switch it up if y'all like. Just trying to get my 4-month-old PR unblocked
yet again 😆😭

For context, see bahmutov/npm-install#146, in
particular [this comment](bahmutov/npm-install#146 (comment)) and linked test output.

This is an alternative to remix-run#3587 or otherwise waiting for `bahmutov/npm-install`
to get fixed.
@jenseng jenseng force-pushed the pin-npm-install-workflow-step branch from 9716a58 to f031158 Compare June 28, 2022 22:39
@@ -17,6 +17,6 @@ on:
jobs:
test:
if: github.repository == 'remix-run/remix'
uses: remix-run/remix/.github/workflows/reusable-test.yml@main
uses: jenseng/remix/.github/workflows/reusable-test.yml@pin-npm-install-workflow-step
Copy link
Contributor Author

@jenseng jenseng Jun 28, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

converted to a draft due to this testing chicken/egg problem ... temporarily setting this so the change actually gets tested :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tests passed using this workflow definition: https://github.com/remix-run/remix/actions/runs/2579553824, i've gone ahead and removed this tweak

jenseng added a commit to jenseng/remix that referenced this pull request Jun 28, 2022
We already use `actions/setup-node@v3` which has equivalent caching
functionality that isn't broken for yarn+windows (or yarn 2+ across the
board). So just use that wherever possible. In addition to fixing builds,
this has the added benefit of slightly speeding them up, since we won't
double-cache things (in some cases we had both caches enabled).

Making this PR against `main` instead `dev`, since the jobs explicitly
use `remix-run/remix/.github/workflows/reusable-test.yml@main`, but I can
switch it up if y'all like. Just trying to get my 4-month-old PR unblocked
yet again 😆😭

For context, see bahmutov/npm-install#146, in
particular [this comment](bahmutov/npm-install#146 (comment)) and linked test output.

This is an alternative to remix-run#3587 or otherwise waiting for `bahmutov/npm-install`
to get fixed.
jenseng added a commit to jenseng/remix that referenced this pull request Jun 28, 2022
We already use `actions/setup-node@v3` which has equivalent caching
functionality that isn't broken for yarn+windows (or yarn 2+ across the
board). So just use that wherever possible. In addition to fixing builds,
this has the added benefit of slightly speeding them up, since we won't
double-cache things (in some cases we had both caches enabled).

Making this PR against `main` instead `dev`, since the jobs explicitly
use `remix-run/remix/.github/workflows/reusable-test.yml@main`, but I can
switch it up if y'all like. Just trying to get my 4-month-old PR unblocked
yet again 😆😭

For context, see bahmutov/npm-install#146, in
particular [this comment](bahmutov/npm-install#146 (comment)) and linked test output.

This is an alternative to remix-run#3587 or otherwise waiting for `bahmutov/npm-install`
to get fixed.
v1.8.16 breaks cache miss installs on windows, which blocks any PRs/commits
that change dependencies. Opened bahmutov/npm-install#146
to address the underlying issue, but in the meantime we can pin to the prior
version to get things working again.

Additional context:
- Discord: https://discord.com/channels/770287896669978684/940264701785423992/991085961972707338
- Initial PR affected: remix-run#2027
- Repro/Debug PR: remix-run#3584
@jenseng jenseng force-pushed the pin-npm-install-workflow-step branch from f031158 to fcea942 Compare June 28, 2022 22:54
jenseng added a commit to jenseng/remix that referenced this pull request Jun 28, 2022
We already use `actions/setup-node@v3` which has equivalent caching
functionality that isn't broken for yarn+windows (or yarn 2+ across the
board). So just use that wherever possible. In addition to fixing builds,
this has the added benefit of slightly speeding them up, since we won't
double-cache things (in some cases we had both caches enabled).

Making this PR against `main` instead `dev`, since the jobs explicitly
use `remix-run/remix/.github/workflows/reusable-test.yml@main`, but I can
switch it up if y'all like. Just trying to get my 4-month-old PR unblocked
yet again 😆😭

For context, see bahmutov/npm-install#146, in
particular [this comment](bahmutov/npm-install#146 (comment)) and linked test output.

This is an alternative to remix-run#3587 or otherwise waiting for `bahmutov/npm-install`
to get fixed.
@jenseng jenseng marked this pull request as ready for review June 28, 2022 22:55
@jenseng
Copy link
Contributor Author

jenseng commented Jun 28, 2022

Closing in favor of #3593

@jenseng jenseng closed this Jun 28, 2022
@MichaelDeBoey MichaelDeBoey added the duplicate This issue or pull request already exists label Jun 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed duplicate This issue or pull request already exists
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants