It's been an half hour now and I'm still stuck at setting up base environment 🙃 can anybody help me
I tried changing the network
Task manager is also okay
Related
I am trying to install Anaconda in my windows PC, installation is stuck at "Setting up package cache" step for almost 14 hours now. Not sure if there is some thing I can do, but this is lot of time for a package to install. I am using my office VPN network, how ever this should not make it run for ever.
enter image description here
In my case when the installation stuck at the same phase for the next attempt I've chosen the installation for user only (not for all users). It also took ages to install but it went through.
Related questions:
Anaconda Installation stuck at - 'Setting up the package cache'
I couldn't install anaconda fully. It doesn't get complete even after half a day. What could be the problem here?
The installation was taking too much time, so i opened the task manager. It helped me sotring out what was eating up the disk(in my case) and it was chrome installer(in my case). So just check out on task manager.
In my case, I saw in the task manager under Conda processes, two CDM stuck tasks, I closed both of them and the installation continued with no issues.
I recently installed Maxima (5.45.0-Windows) on my 64bit, windows 7 machine, following the guide here.
However, when I try to use the GUI, wxMaxima I get an error on launch, saying that the maxima.bat file could not be detected, and it suggests that Maxima was not properly installed. The error message in full is;
"Can not start Maxima. The most probable cause is that Maxima isn't installed (it can be downloaded from https://maxima.sourceforge.io) or in wxMaxima's config dialogue the setting for Maxima's location is wrong."
However, in the Edit-Configure-Maxima menu, under Maxima program I have the path C:\maxima-5.45.0\bin\maxima.bat which should be correct. In fact, when trying to run maxima commands through the command-line promp or through xmaxima, it works just fine.
The GUI however, fails to recognize my maxima.bat file, even when moving it to a different place and 'user specifying' the path, the GUI console is stuck on
Maxima Excited...
Restart Maxima with 'Maxima-Restart Maxima'
But trying to restart Maxima has no effect. Restarting the entire GUI program, or running it as administrator doesn't help either.
I've searched the web for this, but all the search results seem to concern Linux installations or a connection error wrt. internet, which doesn't seem to be my problem here.
i have encountered the same issue (previous versions, now also 5.45.1 on windows 10). in my case this is resolved by manually deleting the "user config files" under %USERPROFILE%\maxima. these files are left over from the previous version & not removed by the un-installer.
try one of the following, then start wxmaxima again.
[command line] del %USERPROFILE%\maxima*.*
[explorer] C:\Users<your user ID>\maxima
I got a new Surface Laptop 3. I typically use a MAC but need windows for a few things. I have been using parallels but decided to bite bullet and get real windows machine.
I use firebase and got firebase-tools installed and running fine. But when I tried to login (using firebase login for the CLI, I keep getting the error message as shown above: Assertion failed: new_time >= loop->time, file c:\ws\deps\uv\src\win\core.c, line 309. I have used bash and powershell with same result. I also logged into a cmd prompt as administrator.
I have searched and searched and found a few things related to the clock and checked that. I also ran some filesystem checks etc. But nothing works. It all works OK in my Windows 10 envioronment under parallels on my MAC but this new laptop cant deal.
Can someone point me in the correct direction?
Looks like its an Ice Lake, Nodejs conflict of some sort. I was having this problem for months with my new HP spectre x360.
Seems it's been patched a few days ago in node: https://github.com/firebase/firebase-tools/issues/1772
I just updated my node install to 12.18.0 (I was on 12.16.1) and I'm no longer getting the error when I attempt firebase cli commands. Hopefully a node update will work for you as well: https://nodejs.org/en/download/
Update the Node!!!
in my case it was v14.4.0 and it was throwing the same error
new_time >= loop->time, file c:\ws\deps\uv\src\win\core.c, line 309
and i updated the node to v14.8.0 and it worked fine.
I was having the same issue. After a loooooong search, I decided to try with WSL (Windows Subsystem for Linux). Once it finished, I installed node and firebase tools using it.
That is the only way that I found to solve this problem. Hope this will be helpful!
I had the same issue on my Windows10 x64 machine (Surface Pro 7) with one of my NodeJs projects. I've installed the latest surface pro fireware update (https://www.microsoft.com/en-us/download/details.aspx?id=100419) and updated to latest NodeJS 14.11.x Version (https://nodejs.org/en/download/current/).
now it works :)
for vm virtualbox win 10
I had the same issue on Windows 10. I simply synchronized the clock.
shut down Windows not restart
start vm (Windows)
go to clock settings "DATE & time"
set button called "Set time automatically" to on
set button called "Set time zone automatically" to on
There is a button called "Synchronize Your Clock" -> click button "Sync now"
And the issue got resolved
I'm trying to automate the provisioning of our developer workspaces which are based on Linux running in a Virtualbox. We also run the IDE inside the Virtualbox. The host system is Windows 7.
The new solution will install the required dependencies (C libraries) and install + pre-configure the IDE (plugins, code formater).
I'm wondering if Vagrant would be the tool of choice for this task. I am irritated since the Vagrant philosophy seems to be: easy provisioning of a dev/test server but running the IDE on the host - not inside the guest. The latter is not an option for us.
What tooling would you recommend for our purposes?
This is the answer to my question. I eventually went for Vagrant.
This simple switch let the normally hidden Virtualbox GUI appear:
v.gui = true
More details here: https://docs.vagrantup.com/v2/virtualbox/configuration.html
My experience with the solution was generally ok. I got my recipes version controlled as wanted. However, the feedback loop was quite long. To build the box with all my customization it took me about 7 minutes which was usually wasted waiting time. When changing a little bit I could try to execute just the changed scripts but to see the whole thing I had to rebuild the box - another 7 minutes wasted waiting.
I am currently trying to understand how in the world of infrastructure as code you still get acceptable feedback loop (let's say below one minute). I assume this is where you enter the world of configuration management with tools like Ansible or Puppet.
I've searched and tried to solve this on my own for a while but I cannot seem to get the Windows SDK 7.0A nor 7.1 to install. Prety much as soon as I execute the setup (NOTE: ISO or web installer) I get the error message "Absolute path information required". Even after I close the message I can see the setup leaving two processes in task manager until I kill them myself - Setup.exe and SetupSDK.exe.
I have found someone who solved similar problem by changing paths in registry for ProgramFilesDir, but in my case it looks correct. I noticed though in my environment variables that the TEMP and TMP were not absolute paths, so I changed them to absolute ones, rebooted computer and tried again but to no avail.
The setup does not even seem to create a log file before the error occurs. Any ideas?
It is a remote PC running Win7 x64
Alright, I finally solved the problem! Phew :D
Turns out I was on the right track at least, and I shall provide the answer which helped me, especially since I could only find one related error when searching the web, concerning Windows SDK, and it was not able to solve my problem.
Solution which worked for me:
Go to regedit.exe
Navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
Make sure basically that every folder there starts its path with "%USERPROFILE%\"
Run Setup again and voila!
In my case, the "Desktop" and "Favorites" entries were set to being only "\Desktop" and "\Favorites" respectively, for some reason. By changing them to "%USERPROFILE%\Desktop" and "%USERPROFILE%\Favorites" I could then run the setup successfully.
Hope this might help someone else!