Upgrading to Beta 4 - keystonejs

I have upgraded keystonejs from 3 to 4 per the instructions. Installed Jade and underscore. New db, got populated. When i start, no errors, waiting on port 3000. Just this error in browser
Cannot GET /
I've looked at the keystone.js and routes files in the demo project, can't figure out the issue.

Related

httpd.exe-The application was unable to start correctly (0xc0000005). Fix?

First of all, im running a Windows 64bit OS. I was having WAMPServer 2 and all of the modules were running good. I knew about WAMPServer 3 and decided to upgrade to it. As of its documentation, we should uninstall the old version , requires all updated Visual C++ Redistributable Packages and i did it as it said.
Checked WAMPServer 3 requirements and also checked with their check_vcredist tool and the result was good. I installed WAMPServer 3, all other modules were working but Apache is not opening and throwing a error message-"The Application was unable to start correctly(0xc0000005)". Apache worked properly in WAMPServer 2.
If anyone's got a solution, please respond to the topic!
Try using System Restore to restore your computer to an earlier successful time

Prestashop does not run locally (XAMPP, Windows 10)

I migrated prestashop 1.4 (all the files) from the live site, to my computer and imported the database successfully to htdocs/prestashop
Now I go to http://localhost/prestashop/ and it shows nothing but this
"This page isn’t working
localhost is currently unable to handle this request. HTTP ERROR 500"
You are trying to run PS 1.4 on php7.
mysql_connect was deprecated in php5.5 and completely removed in php7.
http://php.net/manual/en/function.mysql-connect.php

unable to access index for repository

About the title issue (impossibility to access the package repository from R 3.3.3), now I tried to install version 3.1.1 again: it works and all the repositories can be reached.
Are there any environment variables or registers whose differences between the two versions I can check?
An update. I tried other R installations on different PCs.
I remind that the question concerns impossibility to connect to any package repository (even if packages can be downloaded by a browser and then installed locally).
So I resume the results so far obtained:
3.1.1 "Sock it to me" - windows 8 not proxied - ok
3.3.1 "Bug in your hair" - windows 7 proxied - ok
3.3.1 "Bug in your hair" - windows 8 not proxied - notok
3.3.3 "Another canoe" - windows 8 not proxied - notok
3.3.3 "Another canoe" - windows 7 proxied - ok
So, it seems something come with version 3.3.x which likely does not like windows 8, even if I do not know any reported incompatibility.
Unfortunately, my current working machine is precisely the windows 8 machine ...

PHPStorm crashes for no apparent reason

I am using PHPStorm 9 and crashes all the time.
I checked for logs but it does not report anything.
What can I do to debug it?
Edit 1
The app is fresly installed, on freshly formated PC, with fresh installed and updated java.
Also I tried to increase the allocated RAM but each time the app starts returns my values to default.
Edit 2
I am using the 64bit version which demanded an external jdk since there wasn't provided by the app.
I installed the 8.60 X64 java and add to my user and system vars on windows 10.
Edit 3
I am using Eset's nod32.
This is a notice that shows when I load the app.

Worklight 6.1.0.1 fixpack failed to install on WAS 7

I have installed WAS 7.0.0.31 and trying to update WL 6.1.0 to 6.1.0.1 using IBM Installation Manager. WAS processes were stopped.
All IIM steps went fine, and the final step - click the Update button.
It made some progress (see the screen) and stuck.
After some period of time (like 30 minutes) I decided to click Cancel (see the screen) - it did not help.
So, what am I now expected to do? Are there any logs which Worklight post-install script may write, or can I manually run this port-install script?
P.S. Before this I updated Worklight to 6.1.0.1 for WAS 8.5 Liberty Profile on this machine, which completed fine.
P.P.S. Rebooted, re-tried and left for 1 hour, and it seems successfully completed this time. How can I check fixpack version level for Worklight server? Any property file?
P.P.S. Rebooted, re-tried and left for 1 hour, and it seems
successfully completed this time. How can I check fixpack version
level for Worklight server? Any property file?
I do not believe the server holds any "property file" with the version number.
You can check this in 2 ways:
You should be able to see this in the IBM Installation Manager, it should list what is already installed... 6101 (for 6101 or 6101+ifix).
A bit more involved, but you can deploy a .war, and in Worklight Console you can then click on About, there you will see the server version.