-
Notifications
You must be signed in to change notification settings - Fork 367
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
netlify lm:setup
crashes
#514
Comments
@ehmicky @erezrokah is there any workaround or solution for this? I met this too. |
Sorry @daixiang0, but we haven't been able to look into this yet. |
I am having the same problem on Windows 10 and Powershell 5.1. Running My netlify-cli version is |
Thanks for the additional information @naavis. We're in the process of moving https://github.com/netlify/netlify-lm-plugin into the CLI repo. We'll consider this issue during the migration |
I'm seeing exactly the same problem on Ubuntu 20.04. |
i'm seeing this exact same problem on macOS 11 |
I'm experiencing this on both macOS 11 and Ubuntu 18.04. I'm using Node v14.x on both machines. However, I've examined this a bit and it appears this issue could be caused by a backend issue with the API. The line causing the error as referenced in the OP (mine doesn't show the stack trace) points to calling the
The docs state that This doesn't excuse the fact that the script assumes it found an account without checking the result. A more user-friendly approach would be to check that |
We've been able to reproduce the issue and we're working on a fix as we speak. We'll update this issue as soon as it's fixed. Thanks for your patience and for the detailed information! 🙌🏻 |
Sorry for the trouble everyone. While we figure this out can you try the following workaround cd ~/.local/share/netlify-cli
# on Windows this should be `cd %LOCALAPPDATA%\netlify-cli`
npm i @netlify/cli-utils@latest
# yarn also works
yarn add @netlify/cli-utils@latest
netlify lm:setup |
Ubuntu 20.10 here. After updating to
|
never mind - I can see that path in your log. Can you config the new version is used by running |
Yes, I did, and this is what Here you go @erezrokah
|
@raphink yep, that doesn't look right. Let me see if I can find the correct place to force an update to that dependency. |
FYI, I just tried forcing it system wide with |
I believe some people have reported using an auth token copied from the web UI resolved the issue for them: https://docs.netlify.com/cli/get-started/#obtain-a-token-in-the-netlify-ui |
Thanks @overlordofmu I totally overlook that angle. That should work |
It is only a workaround but it does get some people "working" again while a fix in the CLI tool is being developed. |
Hey @overlordofmu, could you expand on this? Setting this env var does not make any difference for me:
Is this what I should be doing, or is the workaround different somehow? |
Hey everyone Found a workaround that worked for me on Mac.
I suspect for me is because I am behind some versions on npm maybe since running Hope it helps some of you. |
Hi all 👋 and sorry for the delay in fixing this.
|
- Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
netlify lm:setup
crashes.- If the current behavior is a bug, please provide the steps to reproduce.
I ran the following commands in order:
apt-get install git-lfs
git lfs version
netlify plugins:install netlify-lm-plugin
netlify lm:install
netlify lm:setup
All commands worked except the last one which shows:
- What is the expected behavior?
netlify lm:setup
should not crash- Local Environment Information
Paste the results of
netlify status --verbose
hereThe text was updated successfully, but these errors were encountered: