Open jorisvandijk opened 1 year ago
I worked around this by doing jank stuff. https://gitea.krutonium.ca/Krutonium/NixOS/src/branch/master/user/krutonium-hm-extras/packages.nix#L11-L22
I worked around this by doing jank stuff. https://gitea.krutonium.ca/Krutonium/NixOS/src/branch/master/user/krutonium-hm-extras/packages.nix#L11-L22
Thank you for the suggestion. I gave it a try, but am not familiar with "jank stuff". I did the following, which did not work:
home.packages = with pkgs;
let
riderScript = pkgs.writeShellScriptBin "rider"
''
${pkgs.steam-run}/bin/steam-run ${pkgs.jetbrains.rider}/bin/rider
'';
rider = pkgs.jetbrains.rider.overrideAttrs (oldAttrs: { meta.priority = 10; });
in
[
steam-run
jetbrains.rider
...
];
Any suggestions @Krutonium?
I should add I also tried without the pkgs. in front of each package as I run home.packages = with pkgs;
EDIT:
Interestingly, running rider with steam-run rider
from terminal did allow me to log in. Unfortunately re-running it without steam-run breaks it again. For now I can manually run it with steam-run, but that's not really a solution to this bug.
You need to add rider
and riderScript
to your packages; and because of the implicit usage, you don't actually need to install steam-run
or jetbrains.rider
.
Basically what we're doing is replacing the rider
that everything normally calls with our own that runs the proper executable through steam-run
. (Decreasing the priority of the jetbrains.rider
package allows us to overwrite it)
The error message is bad, it has nothing to do with logins. The file ~/.local/share/JetBrains/Rider2022.3/github-copilot-intellij/copilot-agent/bin/copilot-agent-linux
is pointing to the wrong dynamic linker and needs to be patchelf'd.
$ nix-shell -p
$ patchelf --set-interpreter $(cat $NIX_CC/nix-support/dynamic-linker) copilot-agent-linux
You'll have to repeat this step after every plugin update and ideally after every system update because $NIX_CC can get garbage collected.
Would it be possible to nix
ify the plugins, similar to eg Gnome Addons?
You'll have to repeat this step after every plugin update and ideally after every system update because $NIX_CC can get garbage collected.
That sounds very annoying to be honest. I'd second the motion of @Krutonium to Nixify :) (Obviously I have no idea how much of a hassle that is, probably way more than I'd imagine)
Thank you for the reply!
You need to add
rider
andriderScript
to your packages
Yep, that did it! Thanks!
@Krutonium Have a look at #223593
Same bug in WebStorm.
same in phpstorm
Not sure if something else changed. But after moving to unstable at installing nodejs_22 i can now use copilot in rider.
Not sure if something else changed. But after moving to unstable at installing nodejs_22 i can now use copilot in rider.
This fixed my issue as well.
Describe the bug
I'm unable to use the Copilot plugin in Rider as it won't let me log in and throws the following error:
"Failed to initiate the GitHub login process. Please try again."
Steps To Reproduce
Steps to reproduce the behavior: I am following the steps as provided in the official documentation.
Expected behavior
I would expect it to open a webbrowser and let me connect the GitHub account to Rider.
Screenshots
Additional context
I can manually connect my GitHub account in the settings in Rider, but that is apparently not enough for the Copilot plugin.
Notify maintainers
@raphaelr
Metadata