I originally posted this to the Continuum github but didn't get a response, so thought I'd try stackoverview.
I have been trying to create a Python 3.4 environment with the latest installer, which I managed to get through the early part fine. It downloads the first few packages but hangs at 99% then subsequently times out when it gets to this package.
https://repo.continuum.io/pkgs/free/win-64/qt-5.6.2-vc14_3.tar.bz2
I can download it manually in Chrome but it has a similar behaviour - getting stuck at 55.2/55.3mb and stays there for a while before completing. I'm behind a proxy but I do have the correct proxy settings in .condarc. Is there a way to change the timeout limit when I'm downloading it through conda?
Cheers
I had the same issue. In conda < 4.3.0, the timeout was hardcoded to 60 seconds. In Windows, I'm guessing, that's not enough for huge package with a lot of binary files like qt since most likely the virus scanner kicks in to check the files. You can hack your ~userid\AppData\Local\Continuum\Anaconda3\lib\site-packages\conda\fetch.py and change the hard-coded constant yourself, eg. from 60 to 300.
With newer version (I'm not sure when this was added, but I see this in my conda 4.3.22), running conda config --show gave: remote_read_timeout_secs: 60.0. So I believe you can modify it by adding it to your ~userid\.condarc file.
Related
I recently downloaded a program that monitors all incoming and outgoing connections and let's me assign firewall rules on the fly. It also conveniently checks the code signature of programs to verify I am not unknowingly running a modified program.
Now whenever I try to run python3.6.6, I get this little warning. Me being paranoid, I deny access and as a consequence am unable to confidently use my anaconda distribution which uses this executable.
which python --> ~/Users/me/anaconda3/bin/python
I already compared the md5 hash of the original tarball file with a new one downloaded directly from the anaconda repository and they matched.
I am not sure exactly how to proceed...
Is there a way to manually reinstall python into anaconda without using conda? Or would I be better off deleting my anaconda distribution and performing a fresh install? OR is their an alternative that is much simpler and preferred :)?
Thanks
So I decided to backup my anaconda3 directory and them remove the entire directory which included the python3.6 in question.
I reinstalled anaconda3 with the newest release and littlesnitch reported the same suspicion, this time with python 3.7 as that was the newest version available.
This unexpected result drove me to dig deeper and following my research I came across this https://github.com/Homebrew/homebrew-core/issues/20193 and this https://github.com/Homebrew/homebrew-core/issues/18870.
In summary, it is an invalid code signature, but it's also a bug.
I'm trying to install Joomla 3.x with MS SERVER. I try to press INSTALL button on last step and it just redirects me to the same place and doesn't actually install anything.
https://img.exs.lv/e/z/ezeliitis/Untitled.png
What could cause this? :/
Have you ensured that all the prerequisites were installed on the application server? This is an old post - but check this: https://docs.joomla.org/Configuring_sqlserver - it should lead you to the right solution.
This can happen if you have max_execution_time=30 in your php.ini file. This means a script can run a max for 30 s. Sometimes database entry takes time gretaer then 30s. So the installation halts. What you need to do is change it to a higher value in your php.ini file. I kept it max_execution_time=1000.
I have a situation where I need to deploy ruby code to lab devices. These machines are slow and very locked down (hard to get files to). They get re-imaged fairly often, but I am not allowed to bake the install into the image.
I've solved the problem by using the same open ports for Git code distribution to distribute my install files.
I have a long install process boiled down to 3 batch files, but if I could reduce it to one, it would make life a lot easier (not to babysit a lot of installs via VNC). I'm only mentioning all this for reference.
The problem:
I can't install git and then do a pull from command line without opening a new cmd prompt - I think it pertains to environment variables, but am not 100% sure.
I get "git is not recognized" blah blah blah if I don't break out at this point and start the next batch. Same deal when I install ruby and don't break out before starting the DevKit install.
Powershell is not an option (I'm only allowed to install Git, Ruby, and the support (DevKit, C++ redistributables, .Net Client 4) and some of the machines do not have it.
I did a version where I scripted reboots and moving the batches into startup progressively - it works, but some of the other machines are tied together in a way that makes rebooting an issue (please don't make me explain - it's complicated lol).
Is there a way to merge my 3 batch files and execute all steps without reboots?
Edit: I have tried starting the next batch from the first (Start... Call...), and even creating a scheduled task to execute the next step. Can't swear I haven't made any mistakes, but they all seem to inherit the initial conditions and don't recognize the "git" command unless a new cmd prompt is opened.
I am trying to install latest version of Prestashop and it fails when installing modules.
I get no error description, just that modules could not be installed and that I can try again.
I am answering my own question because maybe some day someone finds this useful.
I did some debugging to see where did the installation fail, and it was giving an error complaining about calling the install() method ona non-object variable.
I changed some php code in the modules install script, and I saw it was failing in the statnewsletter module.
I did not knew why was that, so what I did is go to the FTP and check the files of that module, and surprise, all files had 0 bytes size!
So, the porblem was that my FTP client (Filezilla) did not upload the files correctly.
I've uploaded all the prestashop files again overriding all files and then the installation worked fine.
What I've found on the web is that Filezilla can leave the file with 0 size if the server doesn't respond on the 20seconds timeout limit. And that the timeout limit can be increased in Options to avoid this happening.
Hope helps someone!
I've got an MSI based install that I've wrapped in an EXE file as per my installation packaging software (which is Wise Package Studio 7.0 SP2).
I've made many changes to the install, and every time I've tested them, they've worked just fine... up until now.
I changed some text on a dialog box for when the installation finishes and now it seems that no matter how/where I run the installation from, it won't take my "new" version. It continues to "think" it's already installed and even shows an older iteration of my dialog text at then end of the removal/repair/modify.
It's almost like it's cached that MSI/EXE somewhere and instead of running the one I've recompiled (and fixed the message/made changes) it continues to run the "old" one from somewhere.
Any idea what to check for/what could be going on here? Is there windows folder I need to go check? I'm on XP SP2.
Try running on a different machine, this will definitely rule out any local caching.
Check that the changes you have made are actually in the MSI. (use Orca to do this.)
Okay, so I tried this using an XP VM and taking a snapshot before installing. Looks like somehow the previous install was corrupt and was somehow caching itself on the original test computer I was working with.
By going to a clean and fresh PC, my changes were there and the script worked as expected. Now, I don't know what happened to cause the installation to cache like that somewhere on the PC, but at least I found a resolution.
I'll update this question with the location of the cached files if I can track them down...
To remove any cached Windows Installer information, you can use MSIZAP. My guess is that you haven't changed the package code so windows sees it as the same version of the installer (I'm not sure about WISE, but InstallShield is usually configured to automatically change the package code each time you rebuild.)
As far as the location of the cached files, this is configurable so have a hunt around in WISE and you should find it.