I have an issue with nodeclipse: I am unable to run even the simplest demo app (simple require http). When I try to run my "app.js" as a node application, I am just getting:
<terminated, exit value: -1073741819>Node.js Process
When I try to run from the command prompt node app.js, everything goes fine. Did I forget anything important ?
Thanks in advance for your help.
Here is some additionnal informations:
Env config: Win 8 64 bits + Eclipse Kepler 64 bits (JRE 6.0.390.4)
Enide from Eclipse marketplace (based on Nodeclipse 0.9.05)
NodeJs v 0.10.24
While this problem arise from time to time, the exact cause is not yet known. More feedback is needed.
(Once the problem goes away there is no way to reproduce healing; so the only way is to collect data in what environment, and how was solved)
Check Nodeclipse Online Help - Run page
There are 2 similar issues raised before.
#72, #176 was solved via Java upgrade to 1.7
#107 was solved via running node --debug-brk app.js from console first.
Related
I run my pytorch code well on mac and even on windows system but the same code seems stuck on CentOS6.3.
I debug with ipdb, and found the code was stuck at F.conv2d function:
> /home/work/anaconda2/envs/PyTorch/lib/python2.7/site-packages/torch/nn/modules/conv.py(301)forward()
300 return F.conv2d(input, self.weight, self.bias, self.stride,
--> 301 self.padding, self.dilation, self.groups)
302
ipdb> s
The running env was created with anaconda(python 2.7/3.6), pytorch version is 0.4.0.
I tried for a long time to resolve this problem and i tried. Do you have a suggestion? Thank you so much!
I reinstall CentOS6.3, and then upgrade glibc2.14, glibc2.17 due to the pytorch0.4.0 running error info.
Now everything is ok.
By the way, the pytorch0.3.1 perform well before i upgrade the glibc(up to 2.12). So i think the lastest pytorch0.4.0 may haven’t deal very well with glibc, leave running deadlock appearance and doesn’t tell any error and warning info, just stuck at F.conv2d in torch/nn/modules/conv.py(301).
See also: https://discuss.pytorch.org/t/f-conv2d-stuck-on-my-centos/19794/3
I've been having problems getting debugging working with this setup for the past year. Supposedly, this is fixed in the latest versions, but I just can't seem to get it to work.
I'm using Mac OSX 10.8.5, Eclipse Keplar, PyDev 3.0.0, and Google App Engine 1.8.8.
I set up a run configuration to point to dev_appserver.py, running my project. That works fine. My python version is 2.7.3, and everything works in normal mode. When I try to run in debug mode, however, the app runs, the output specifically states:
pydev debugger: starting
pydev debugger: google app engine integration enabled
But after 20 seconds, the python process terminates with this error message:
'Launching New_configuration' has encountered a problem.
Timed out after 20.0 seconds while waiting for python script to connect.
Accept timed out
Execution works during those 20 seconds, because I can hit URLs connected to my app and see an effect. Breakpoints do not work, though. Is there something I need to do to get python to 'connect'?
Also - I should note that switching back to using 'old_dev_appserver.py' fixes this problem - debugging works fine when I do this. But, this is not really a solution, because I need to use the latest socket additions in the newer releases.
Thanks for any advice.
temporary solution:
edit the pydev_app_engine_debug_startup.py file:
eclipse/plugins/org.python.pydev_${VERSION}/pysrc/pydev_app_engine_debug_startup.py
change the line that reads:
if ':' not in config.version_id:
to:
if ':' not in config.version_id or config.version_id.startswith('default:'):
Looks like this is fixed in 1.9.0. I also had to make sure to update PyDev to the latest (3.3.3 at the time of this writing).
One more thing to add, and this one really tripped me up (on MacOS) -
In Eclipse, under Run -> Run Configurations, set the Main Module to point to this location:
/usr/local/google_appengine/dev_appserver.py
NOT the symlink:
/usr/local/bin/dev_appserver.py
Well, finally I found the answer. It is a Google's bug.
It has been reported and acknowledged.
see Debug is not working with PyDev again 1.8.8!
Update: Until the bug is fixed I am using PyCharm. The pro version has 30 days trial and works with GAE. It works like, well, a charm. I may even consider switching to it from Elicpse/PyDev
But I am used to JetBrains tools with Android Studio recnetly, and WebStorm and Resharper in the past, so I know to find my way around their IDEs. Your milage may and will vary.
Since the question, a new GAE has been released 1.8.9
Running GAE 1.8.9 with PyDev3.3.3 on Windows8.
This timeout issue still occurred.
When I entered the temporary workaround changes to pydev_app_engine_debug_startup described in the earlier answer, then the browser could not connect to the app.
However, on backing out this change, not only did the 'Launching New_configuration' not appear, but the breakpoints worked.
More info on the Python Tool Support for the App Engine Development Server is here
https://docs.google.com/document/d/1CCSaRiIWCLgbD3OwmuKsRoHHDfBffbROWyVWWL0ZXN4/edit
I am running ubuntu 12.04 64 bit, I have set up FB4Linux (FlashBuilder for Linux) and installed the »flash-installer« installer plugin via »apt-get«. I downloaded the latest version of the plugin-debugger from adobe and followed the install instructions from the included README.txt file. Running eclipse (Version: 3.7.2, Build id: I20110613-1736), creating a new as3 project works, build works, everything fine, I can start the debugger and step through the code BUT after a while the debugger just disconnects and stops. No error, no crashes, debug session just over.
Any Ideas?
.log
about:plugins:
Flash - Version: 11.2 r202
Shockwave Flash 11.2 r202
I think , this is happenning more fequently due the enhanced breakpoint listener support in eclipse.When a breakpoint is removed, it is trying to notify its "breakpoint specific" listeners, which were stored in the breakpoint. Of course, this will not work since the underlying marker has been deleted. but things will happen after removing break point. so one way to resolve this problem is to try to un-select
Window > Preferences > Java > Debug : Suspend execution on uncaught exceptions
may this will help you!!
The solution to this issue occurred as side effect after I applied the changes from the answer of this question. When I tried to set the compiler options to target version 11.2, which is actually installed on my system errors occurred because their were files missing in the sdk folder (which are the described changes) and I could only develop for version 11.1. Kind of wired but the update of the sdk made the debugger run stable.
SOLVED - See bottom of post
Firstly, I will state that I have read all the existing posts regarding this problem and none of the suggested solutions have worked.
After upgrading eclipse to Indigo SR2 and to java 7, I was not able to start Glassfish, either embedded or separate installation.
After a week of this and because my PC was getting sluggish, I decided a full rebuild of my PC was required, so I reset the PC back to factory settings and started again.
My spec now looks like this...
Windows XP SP3 - Firewall Disabled as 3rd Party solution installed
Java 7 - jdk1.7.0_03 + jre
Eclipse Indigo SR2
hosts file...
127.0.0.1 localhost
I installed the latest Glassfish Plugin from: http://download.java.net/glassfish/eclipse/indigo
However, just as before the rebuild, when I try and start the server, I get the CREDENTIAL_ERROR.
I'm now super frustrated as I would have expected this completely clean install to just work.
I disabled the firewall, but that made no difference.
I then tried to start the embedded server manually. e.g. asadmin start-domain, and it started fine. I can stop it from Eclipse, but as soon as I try and start it again I get the CREDENTIAL_ERROR. Grrrrhhh!!!
I also spotted this entry in the eclipse .log file...
!MESSAGE GlassFish: error reading one jmx portjava.lang.NumberFormatException: For input string: "${JMX_SYSTEM_CONNECTOR_PORT}"
...which may be relevant as the final line of a verbose manual startup of the server looks like this...
[#|2012-04-09T15:33:16.625+0100|INFO|glassfish3.1.2|javax.enterprise.system.jmx.org.glassfish.admin.mbeanserver|_ThreadID=41;_Thre
adName=Thread-23;|JMX005: JMXStartupService had Started JMXConnector on JMXService URL service:jmx:rmi://HOME:8686/jndi/rmi://HOME
:8686/jmxrmi|#]
Many thanks
Chris
SOLVED
Darn it. Just after posting this, I stumbled upon this link...
http://java.net/jira/browse/GLASSFISHPLUGINS-72
...which suggested that the Anti-Virus (not the firewall) being the culprit and lo and behold, it was. I removed port 8080 from scanning and the server fired up without a problem.
Now I need to work out if I've opened up a security hole.
UPDATE
I decided to install a separate Glassfish instance and the problem started over again. In then end I discovered that I had to disable the NOD32 HTTP Scanner entirely to allow the server to start. Re-enabling it got the CREDENTIAL_ERROR again. There didn't seem to be any configuration setting that would get around this. I'll have to fire an email off to ESET to see what they suggest.
I'm working with about the same configuration. Only my eclipse is Version: Indigo Service Release 1, and I work in an environment where it isn't allowed to disable a firewall.
In my case it helped to switch to a previous version of Java (jdk6-u30), which wasn't what I intended. So I installed the newest version of the JDK at this moment: jdk1.7.0_04, and used this as the -vm value in de eclipse.ini.
This still left some complains about a Currentversion of 1.7 when 1.6 was expected by our version of Glassfish's asadmin. Which were worked around by changing the registry back to 1.6, instead of the 1.7 version added by the installation of the jdk1.7.0_04.
After these changes I could start and stop Glassfish from within eclipse without the CREDENTIAL_ERROR.
First of all this question has been asked at least twice.
I tried several approaches with no effect.
Here's the problem:
When I try to download/update plugins like EclEmma, Eclipse starts to communicate with the repository and that takes about 5 minutes. After that I get an error:
"An error occured while collecting items to be installed
session context was:(...)
Unable to read repository at http: (...)
Read time out
(... for every *.jar)"
What I was trying to fix the problem was running eclipse as an admin (got vista x86 running) and changing the connection properties from native to direct and back. I also tried deleting saved repositories and adding again. No effect at all.
I have no proxy configured and don't need one.
This is getting kind of personal between me and my IDE :D
So I hope you guys can help me out.
Thanks Zoltán (köszi :D), but i found the error last night.
Resolution
After hours of debugging I figured out that AVG Anti-Virus Software blocks the request. After deactivating it for temporarily, Eclipse installed the new software.
In my case timeout was caused by definition of SOCKS proxy... we have proxy.company.com:80 and I incorrectly provided that proxy to all three (HTTP, HTTPS and SOCKS) connection schemas. Removal of proxy from SOCKS resolved the problem
Try to open the internal web browser of Eclipse (Window menu/Show view/Other...), and navigate to the 1) update site url, and 2) to any webpage.
If the latter one is not working, then Eclipse does not have connection to the internet, and you should try to open a new workspace, and try installing from there (possibly something wrong in the workspace settings).
If the second one works, but the first one does not, that suggests that the update site is not working. In this case report to the developers.
I also had this problem (my system: Win7, jdk7, Eclipse Indigo).
I installed jre6, changed my JAVA_HOME, ran eclipse with the following:
eclipse -debug -consolelog -vm 'c:\Program Files\Java\jre6\bin\java.exe'
Install the plugins/updates, then switch back to using jdk7.
Worked for me!
Temporarily disabling AVG firewall fixed the issue for me.
Eclipse then installed the Android plugin.
In my case, adding these lines to eclipse.ini solved the problem
-vmargs (this one was alreayd there)
-Djava.net.preferIPv4Stack=true