-
Notifications
You must be signed in to change notification settings - Fork 21
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
download errors/issues #86
Comments
@stereomato, which platform do you use?
|
"x86_64-linux" I've switched from using home-manager as a module to it being standalone and coincidentally this seems to be fixed. I'm confused honestly |
I was mistaken! And no, #87 does nothing. This issue seems to be triggered if a beeg download is also happening alongside the extension downloading. Like, I just reinstalled NixOS, and when installing my home-manager profile, I had constant vscode extension download issues, so I disabled that and, and saw that davinci resolve was being downloaded. Once h-m finished installing, I reenabled vscode + extensions and voila, the next generation went smoothly. |
@stereomato, please close this issue if it's is resolved. |
It comes and goes, as I said, if something heavy is also being downloaded thru nix. So it can be worked around, not truly fixed :/ |
Just got it right now, lol |
|
@stereomato Which nix version do you use? |
nix (Nix) 2.24.12 nixpkgs/nixos unstable |
@stereomato I don't have this problem with nix 2.26.1 and single-user installation. I believe nix-vscode-extensions is not the root cause of your problem since I haven't seen regular complaints about this problem from users of nix-vscode-extensions. Additionally, I can't reproduce it. NixOS/nix#1362 may be relevant (see NixOS/nix#1362 (comment)). |
Hm, alright thanks. It's a bit annoying though, it's easy to "deal" with this by just running the rebuild command again, but it doesn't feel proper. |
Essentially every time I update and there's a lot of things to download, I get errors like this:
Is there a way to fix or workaround this?
The text was updated successfully, but these errors were encountered: