im getting this error when im trying to update Meteor on windows.
Using git bash here, but getting the same error in command prompt.
Does the file simply not excist, or what is going on here, have had it for some days now, so im just curious if the file excist at all, since its not really officially supported on windows yet?
$ meteor update
New version available: 0.3.8
Failed to download: https://d3sqy0vbqsdhku.cloudfront.net/meteor-package-Windows
_NT-i686-0.3.8.tar.gz
It is not supported officially yet on Windows. You need to rely on weekly checking win.meteor.com for updates.
I believe you are correct in your assumption of it not really being officially supported on windows. I also get this same error and have tried everything to get around it. I tried scouring for this package manually and was unable to find it.
Related
Can anyone help me out whilst I still have some hair left.
I have been running VSCode on Windows 10 since January. Yesterday it attempted to update to the latest version 1.54 but failed. VSCoce will now not run.
I am trying to re-install from the VSCode site installer. However when I download and run the installer file windows gives an error saying the file is corrupt.
Windows Error Message
I seem to remember having this problem when installing the 1.52 version in January but I can find no reference to what I did to resolve this. I believe I was pointed to an alternative install program, but I cannot find this now.
Please can anyone assist?
Many thanks.
Colin Murdoch.
OK. I have now managed to re-install VScode by downloading the .zip file and extracting all the elements into a directory within Program Files. It remains to be seen if this will work properly as with no official install routine, nothing will have been added to the registry. However the program loads OK and seems to recognise the PlatformIO extension that was already loaded.
I still don’t understand why I cannot run the official install routines. There must be something odd about my Windows installation.
check your antivirus program. I recognize that message. I had the same issue when trying to install an SQL server.
I'm trying to go get go.etcd.io/etcd/tools/benchmark.
Previously this has worked, flawlessly. However when I try to do it currently I have alternatively got no errors and I've had it fail on me with:
go/src/go.etcd.io/etcd/vendor/google.golang.org/grpc/balancer_conn_wrappers.go:28:2: use of internal package google.golang.org/grpc/internal/buffer not allowed
go/src/go.etcd.io/etcd/vendor/google.golang.org/grpc/clientconn.go:49:2: use of internal package google.golang.org/grpc/internal/resolver/dns not allowed
go/src/go.etcd.io/etcd/vendor/google.golang.org/grpc/clientconn.go:50:2: use of internal package google.golang.org/grpc/internal/resolver/passthrough not allowed
The first time I ran it on a new go-1.13 installation it worked, but the following times it has failed as above.
The repo has not changed as far as I can tell in the past 8 months and I've tried on various golang versions but all so far have failed (bar the go-1.13 on that first try...).
Any assistance debugging this would be greatly appreciated!
I have both a workaround and an official fix.
The workaround:
Here I defined a go.mod which then used a previous version of the library.
The official fix:
This was fixed upstream and thus no one else should experience this.
I guess you can try by removing vendor folder from the go.etcd.io/etcd repo. Also disable the vendoring mode. It should work.
I've tried to get this running with versions 2.14.4 and 2.15.2 without success I can run on version 2.13. I'm trying to figure out the issue, step one is as below;
In both versions this is what I see after installing the vectortile extension and restarting but this differs from the screengrab shown in the documentation. So my question is whether the documentation image is out of date or my install has not worked (2.14.4 with Vectortile extension 2.14.4).
I resolved the bug which means I can confirm that the above screenshot does mean that the vectortiles extension has installed properly
When I try to install devtools in Rstudio 3.2.3 (Windows 10) using the command install.packages("devtools"), I get the following message:
warning in install.packages :
'lib = "c:/Program Files/R/R-3.2.3//library"' is not writable
I'm a newby and I've been hunting for solutions but so far am coming up empty. I would appreciate any advice that might get me through this step. Thanks.
I stumbled upon the same issue earlier. This "problem" arises when you try to install a library for the first time and R does not have a a dedicated library for it yet.
Two pop-up should appear one after the other when you try to install a package like:
install.packages("ggplot2")
The questions are the following:
Would you like to use a personal library instead?
Would you like to create a personal library 'C:\Users\bartlein\Documents/R/win-library/3.2' to install packages into?
Answer yes to both questions and you should be fine.
The ressources I used came from here.
I should mention that I originally posted this as an issue on Neovim's tracker, but it hasn't been getting a ton of traction there lately and I'm beginning to suspect that it's more an issue with my setup rather than Neovim itself.
Essentially, I had stopped building neovim nightlies for a few months. Having heard that it's getting integrated terminal support I decided to rebuild using the latest source, only to get a persistent, odd error. No matter what my build settings are, it always boils down to make hitting an error when it has to compile a file called loop.so. I hadn't noticed this issue with any other software I try to build, but I suspect it could be an issue with my environment.
Does anyone here know what this file's role is, and why the compilation could be failing at that point?
You might need to install the full Xcode app and not just the command line. This fixed the issue for me.
The issue turned out to be a bad typedef in a libuv header, object.h.