-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to load resource: the server responded with a status of 404 (Not Found) #28
Comments
Hi thanks for reporting the issue! It looks like you're running the version in npm. Sorry for the inconvenience - it was left in there accidentally. socket.io isn't currently being used, so the error should be harmless if annoying. We're currently going through a bit of a rewrite, switching out the webserver back end for one built on Electron. I should have a better working version merged in a day or two. Let me know if you have any trouble, and I'll be happy to comment on this ticket when there is a new version published. |
Thanks. today i tried with the latest and its failing as follows. Please help OS: Windows_NT 6.2.9200 x64 npm ERR! Windows_NT 6.2.9200 npm ERR! Please include the following file with any support request: |
Sorry, the latest version still isn't quite ready for public use. I'm planning on having a Windows executable eventually through the Electron app integration and a Chrome plugin, but only about half way there right now. If you can ignore the socket-io warning, the version in npm is still better to use for now. I'd like to help you debug this though if you'd like. Right now because of way Electron is written, I can only get things working with io.js v1.8.1 because it uses the same version of the v8 engine as Electron. I'm not sure of that status of that on Windows. Would you mind sharing your npm-debug.log? Usually the problems I've seen on Windows involve the native compiled libraries - currently that's just node-serialport and Electron (possibly). Sometimes those fail because the host computer doesn't have build tools installed. I also see that node-serialport only supports Windows 7 and above. |
Thanks for your quick response. I just started learning the Nodejs. If windows creates problem, i will try in my ubuntu and let you know. Please check my log file for your analysis. |
I tried in Ubuntu 14.10 ~/nodejsws/robotnik$ sudo npm install
[8671:0510/162019:ERROR:browser_main_loop.cc(171)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. "Browser opened blank." when searching the error in google, i got the below url. Need your guidance. |
Thanks for the details! I've downloaded an Ubuntu 14 image, but haven't had a chance to test it yet. If you're eager, I'd recommend trying nvm instead of the node version installed on Ubuntu. https://github.com/creationix/nvm - nvm installs multiple versions of node.js and io.js in your home directory so that you don't need to use 'sudo' to install modules. There is an '.nvmrc' in the repo that specifies the version I use. Once you go into the project directory, you can just: |
Thanks for your suggestion. Following are the observations. nvm install ->then-> nvm ls-remote iojs from stackoverflow.. Did ->then-> nvm install ->then-> rsrini@rsrini-desktop:~/nodejsws/robotnik$ NVM_IOJS_ORG_MIRROR=https://npm.taobao.org/mirrors/iojs NVM_IOJS_ORG_VERSION_LISTING="https://npm.taobao.org/mirrors/iojs/index.tab" nvm install ->then-> sudo npm install All fine (except few warnings - ignored) ->then-> sudo npm start ->then-> Same Issue: Blank Screen [12629:0512/210554:ERROR:browser_main_loop.cc(171)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. |
Hi, |
Pretty sure this is all now resolved with newer versions of electron and node serial port and the pain we had to go through for the last 6 months. Suggest close out as we have this working on OSX, Win and Ubuntu / Raspbian. Also this last issue may well be due to the websockets switch off on chrome that has now been resolved upstream again. Recommend closure of this item. |
Works fine in Ubuntu 14.04. But gulp failed in Windows 8 and 10.
[16:46:35] Using gulpfile D:\robotnik\gulpfile.js events.js:154 |
After installing the robotnik, i am getting error in my chrome console when accessing the URL.
Failed to load resource: the server responded with a status of 404 (Not Found)
http://localhost:8057/socket.io/socket.io.js
The text was updated successfully, but these errors were encountered: