-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
post setup-node throws an error - missing pnpm store dir #543
Comments
Hello @dominikg. Thank you for your report. I think it can't save the cache because pnpm store path returns such output:
It gets extra logging that is why the action can't get correct path. As temporary solution could you please create .npmrc file with such content:
|
hmm, that's very unfortunate and could break a lot of CIs, In fact i wonder why it hasn't caused more trouble until now. Can confirm that the additional logging appears when updating from pnpm 7.5.0 to 7.5.1 cc @zkochan the impact is limited by the fact that not everyone uses |
Have a similar issue and can confirm above too.
|
Hello @RIP21. Could you please as temporary solution add |
can confirm that https://github.com/sveltejs/vite-plugin-svelte/runs/7309633235?check_suite_focus=true#step:16:6 |
|
Hello everyone. I've merged fix in the main branch. Could you please confirm that it works as expected for |
Hello everyone. We released a new version and updated the major tag with fix. Could you please confirm that everything works as expected ? |
apparently, v3 has a fix: actions/setup-node#543
* feat(queryObserver): add isInitialLoading derived flag this flag describes isLoading && isFetching and can be used to show a loading spinner for lazy or disabled queries * chore(ci): fix caching apparently, v3 has a fix: actions/setup-node#543 * chore(ci): properly fix token issue as described here: https://stackoverflow.com/questions/52015748/npm-failed-to-replace-env-in-config-npm-token he extra warn output made the caching fail * chore: fix bundlewatch glob * docs: add a section about isInitialLoading to the migration guide
* feat(queryObserver): add isInitialLoading derived flag this flag describes isLoading && isFetching and can be used to show a loading spinner for lazy or disabled queries * chore(ci): fix caching apparently, v3 has a fix: actions/setup-node#543 * chore(ci): properly fix token issue as described here: https://stackoverflow.com/questions/52015748/npm-failed-to-replace-env-in-config-npm-token he extra warn output made the caching fail * chore: fix bundlewatch glob * docs: add a section about isInitialLoading to the migration guide
* feat(queryObserver): add isInitialLoading derived flag this flag describes isLoading && isFetching and can be used to show a loading spinner for lazy or disabled queries * chore(ci): fix caching apparently, v3 has a fix: actions/setup-node#543 * chore(ci): properly fix token issue as described here: https://stackoverflow.com/questions/52015748/npm-failed-to-replace-env-in-config-npm-token he extra warn output made the caching fail * chore: fix bundlewatch glob * docs: add a section about isInitialLoading to the migration guide
* feat(queryObserver): add isInitialLoading derived flag this flag describes isLoading && isFetching and can be used to show a loading spinner for lazy or disabled queries * chore(ci): fix caching apparently, v3 has a fix: actions/setup-node#543 * chore(ci): properly fix token issue as described here: https://stackoverflow.com/questions/52015748/npm-failed-to-replace-env-in-config-npm-token he extra warn output made the caching fail * chore: fix bundlewatch glob * docs: add a section about isInitialLoading to the migration guide
Description:
post setup-node throws an error about a missing store directory for pnpm
Action version:
3
Platform:
Runner type:
Tools version:
node16, pnpm 7.5.1
Repro steps:
workflow:
https://github.com/sveltejs/vite-plugin-svelte/blob/main/.github/workflows/ci.yml
run with error:
https://github.com/sveltejs/vite-plugin-svelte/runs/7306898304?check_suite_focus=true
Expected behavior:
pnpm store is detected correctly and cached in post-action - no error thrown.
Even if the run completed correctly but for whatever reason the pnpm store could not be cached, post should not throw an error, causing a CI fail.
Actual behavior:
An error is thrown in post setup-node, failing the run
The text was updated successfully, but these errors were encountered: