GitHub Community
-
Select Topic AreaBug BodyI can login fine from my Mac using IntelliJ IDEA Ultimate, but I can't do so from Ubuntu. I don't have a proxy. OS: Ubuntu 22.04.1LTS (arm64) I think these are the relevant log lines: The agent had this output: |
Beta Was this translation helpful? Give feedback.
Answered by
huyl
Dec 3, 2022
Replies: 4 comments 4 replies
-
|
I managed to login. I think I figured it out. Instead of running IntelliJ from a desktop icon, I ran it from the command line using the Ubuntu's default node is very old: But in my shell, I use So yeah, it would be nice if the Copilot plugin did a version check on node and gave users an appropriate error message. |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
I tried using a newer Node version but it didn't work for me. I am launching IntelliJ as follows: [~]$ nix shell nixpkgs#jetbrains.idea-community nixpkgs#nodejs-18_x
[~]$ node --version
v18.12.1
[~]$ idea-community
... IntelliJ output ...When the IDE launches I still get "Failed to initiate the GitHub login process. Please try again." |
Beta Was this translation helpful? Give feedback.
-
|
@danielfrankcom You should look at the error notifications (you know, the same that shows all the Java exceptions, usually due to some buggy plugin) and see what it says for the Java exception and look for the copilot agent's logs which in my case had a node exception. |
Beta Was this translation helpful? Give feedback.
-
|
I enabled debug logging for the plugin by adding I get the following message which doesn't seem to be Node related: |
Beta Was this translation helpful? Give feedback.
-
Also solves my issue with copilot on windows arm edition. Thanks! |
Beta Was this translation helpful? Give feedback.
Answer selected by
huyl
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Wow i can't believe it was this issue :) @huyl thanks !! i upgraded NodeJS from 16 -> 18 and it did succeed to work inside Devcontainer in Intellij .... maybe this should be better fixed to give proper messaage in this error ? do you know who can i contact to ping to fix it in order to save some hours/day for someone who will encounter this issue ? :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
SM-A025F
Pada Sel, 21 Jan 2025 18.37, AvishayHirsh ***@***.***>
menulis:
… Wow i can't believe it was this issue :) @huyl <https://github.com/huyl>
thanks !! i upgraded NodeJS from 16 -> 18 and it did succeed to work inside
Devcontainer in Intellij .... maybe this should be better fixed to give
proper messaage in this error ? do you know who can i contact to ping to
fix it in order to save some hours/day for someone who will encounter this
issue ? :)
—
Reply to this email directly, view it on GitHub
<#40685 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATLHTSALDDVA35YV3XB7EDT2LYWOFAVCNFSM6AAAAABKOTLDQKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJQGE2DIMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I managed to login.
I think I figured it out. Instead of running IntelliJ from a desktop icon, I ran it from the command line using the
ideascript. So I think this gave IntelliJ a newer node.Ubuntu's default node is very old:
But in my shell, I use
nodenvto get a newer node:So yeah, it would be nice if the Copilot plugin did a version check on node and gave users an appropriate error message.