I do not have concurrent builds so there should be no additional lock on any file. My only guess is, that gitlab-runner does mess with the permissions. Is it possible to include in the error message something helpful or even better, an automatic fix, as this is an issue anyone trying to run rustup update in vs code is likely to experience.
There isn't a lot we can do to fix it without introducing other issues instead due to the limitations in Windows. It's possible we could construct a more informative error context though. The Microsoft documentation contains some description and example code for using the API. Note that the API can just be used to detect which process holds a lock on some file similar to lsof and make the error message of rustup more helpful to users.
It is not necessary to actually "restart" the other processes holding the lock. That is very interesting, thank you t-rapp. Closing out of all instances of VS Code and even running Command Prompt as Administrator did not help, but rebooting the computer and rerunning the command did I did not need to run Command Prompt as Administrator after rebooting.
I imagine this means that at least one rustup instance was still present, perhaps as a background process. I'm not certain how to tackle this on Windows safely :. I've now looked into it and I don't think RestartManager is suitable for the problem for rustup.
It doesn't handle the case of new processes starting up during the update procedure. And it depends on throwing up UI prompts for shutting down and restarting things. It's a fine solution for the general case but we can do better in the special case. Skip to content. Star 4. New issue. Already on GitHub? Sign in to your account. However, I think the "Couldn't resolve host name" error is a red herring. I can download the file manually:. The text was updated successfully, but these errors were encountered:.
Hmm, it certainly seems like curl or, c-ares is just not doing the right thing in trying to resolve DNS. However, because when I run curl on the command-line it works fine, I suspect that rustup is calling it somehow differently which causes it to break.
Sorry, something went wrong. Thank you for the report CmdrMoozy! I have no idea what causes it, or if it's happening across all appveyor tests at the moment. This might be related to IPv6, in which case it would be a duplicate of Really weird.
I can download directly from static. But when i try to download using that link in web browser on one machine I get "server not found". Disabling ipv6 via kernel, nm, etc didn't appear to fix things. I'm experiencing this error today. I am not on a VPN nor have a proxy. Curl doesn't seem to have an issue though. LoZeno It would help if you could get a network trace of what rustup is doing when it times out. In this case though, we're aware there's a bug in the proxy code and we're working on getting a fix out ASAP.
Especially important is to consider the error you get if you specify --verbose when updating; and also the kind of proxy you're trying to use. I will open a new issue with it. Skip to content. Star 4. New issue. Jump to bottom. Projects Issue Categorisation. Copy link.
Have this problem solved? I meet the same issue Update stalls at syncing channel updates Diggsey added this to Downloads in Issue Categorisation May 30, When install 1. I meet the same issue. If unset, cURL can't download.
It worked after I disabled network proxy Proceed with installing necessary dependencies? Turned off VPN here Proxy: Cannot download files Sign up for free to join this conversation on GitHub.
0コメント