Yesterday I was perfectly able to debug a rails application using Netbeans 6.9.1 (just clicking on the Debug Main Project).
But now, suddenly when I try to debug I see the "Server Startup" at the bottom... but after 30 secs aprox. a message appears in the status bar saying "Cannot connect to web server, cannot show localhost:3000".
I'm using Windows 7 x64 (yes, I know I should be developing under linux, but I don't have the time to make the transition), Netbeans 6.9.1, Ruby 1.8.7, Rails 2.3.8 and the Fast Debugger (ruby-debug-ide).
I'm a MS/.NET guy trying to migrate to the wonderful world of OpenSource and RoR.... but it can't be to hard to debug.... I'm not asking too much I think =P
Well, uninstalling and reinstalling fast-debug-ide gem solved the problem.
Related
For some reason, Github Desktop just stops working and doesn't launch at all about once a month. When that happens I have to uninstall it and install again.
My OS is x64 Windows 10 Pro. Have anyone any idea why might this be happening?
I used to work with Grails 3 for years now. Just started a new project on version 4.
In this version (not 100% sure if it's version related), when I start the app with grails run-app it runs, but I can't stop it with the regular Ctrl + c.
The only way that I can stop it is by killing the java process.
Did anyone experienced this issue?
I am on Mac OS Catalina and running the app from iTerm terminal.
I am new to Android programming. I have an issue: my PC shutdown while I was working on a program.
When I turned it on I got all kinds of errors. I tried other programs that I created in my lesson (which I took from Internet), but none of them work now. They all give me many errors.
For example:
I think when the PC shutdown I might have lost something, but I uninstalled Android and reinstalled and I get the same thing.
Thanks for any help.
I'm fix
1. uninstall android studio
2. install new android studio and skd again
3. open android project
4. File -> Invalidate Caches / Restart
I am running on Mac Lion 10.7.3 with i5 2.3 GHz and 4GB Ram.
Application is running fine with command line
rake run:iphone
rake run:android
but when I am trying to run the same app using RhoSimulator, app getting crashed just after login.
I looked into all pros and cons but in vain.
First thing first: As the first para of this link suggesting http://docs.rhomobile.com/rhodes/simulator
"RhoSimulator allows to run Rhodes applications without lengthy build process and to debug them in RhoStudio. Currently RhoSimulator works on Windows only."
Is this possible to run rhosimulator on Mac at all?
If yes then please find the crash report and throw some light to fix this.
yes , for me too, for no reason, just 1 week before the same application run in rhosimulator but now have got same crash report as you.
but i can login (http async), but after on one page, rhosimulator crash..
-> uninstall all gem rhodes, and multiple packets gems version..
-> reinstall rhodes 3.2.2
-> got same crash.
-> get and install rhosimulator fix pack
-> got same crash
try to compile for iphone simulator, run:iphone-> ok, inside iphone simulator -> got app go out a the same page (crash i suppose)..
so no understand., it's my third application with this framework, i'm tired to patch the framework and try to get stable working framework...
I recently updated my Snow Leopard to Lion and today, I went to open XCode and it gave me an error saying that the XCode I had wasn't compatible with Lion, or something like that.
Did some research, and ended up installing XCode 4.1 from the Mac App Store.
Well, that was about 3 hours ago, and I'm installing and it says "Updating Files" and the loading bar is almost to the very end of the line. It's been this way for about an hour. Should I quit and restart? Should I just wait? Why is it taking so painstakingly long?
The problem I had was that there was still an iTunes process running.
I could solve this by stopping the 'iTunes helper' process.
After stopping that process the installation of XCode continued and installed quickly.
I had the same problem as #Mark, but I still had to force quit the installer, and try again. The second time through it installed fine.