|
|
|
[
Permlink
| « Hide
]
Chris Williams - 04/Jan/08 01:23 PM
From the log it appears that one of the core Ruby plugins is not being loaded up properly, which could be a cause of the issue. Does this happen every time? if you upgrade to a nightly build (http://www.aptana.com/docs/index.php/Changing_your_update_version_type_of_Aptana
 ), does it clear up?
I don't know - I don't seem to be able to update (see SAS-10)
Fixed: I uninstalled and re-installed Aptana Studio Pro and RadRails plugins, updated to Aptana Pro (Alpha)1.1.10.200712051732 and RadRails 0.9.9.200712220421NGT (the same username and password that were being rejected were accepted - weird) then created a new workspace and my existing Ruby was properly detected.
Actually, not fixed. There is still a problem - and this has cost me many hours of hung systems, re-installations, troubleshooting and stomping around.
I took the re-installatoin action above on a Windows machine, then reported "fixed" ... a bit too quickly - I can't get this to work on my Fedora 8 (main) workstation. First, as to the passwords (re SAS-10) ... I have gone to each of the password entry forms several times and always put in exactly the same password every time. Obviously I can log into the ASAP system, and I can log into the forums, and I can log into my "store" account. I think that means all the passwords are set up the same - does it? Next, on my Fedora 8 installation I decided to just not mess with de-installing and instead go for a complete clean re-start. I deleted my eclipse installation, downloaded a fresh copy of eclipse and installed/updated it in a clean new workspace. I re-downloaded/installed and updated Aptana Pro (and when I put in my license I was asked if I wanted to install the Pro features and said yes, then subsequently updated and supplied my username/password and it seemed to be accepted - I got updated to the 'Alpha' versions) I install RadRails and restart, and I get the 'unable to detect' dialog and hang - and so I can't update any more (or do anything else). Sigh. I'll attached the .log from the new workspace (as 'ruby_hang_after_reinstall.log'), and here's the feature/plugin list: Hi, I'm with the same problem in Ubuntu 7.10.
cipriani@cipriani-laptop:~$ ruby -v I tested with Eclipse 3.3.1.1 and with AptanaStudio distributed by you and the problem occurred on both situations. There is another way to set the Ruby install? Because it seems that Aptana/Eclipse works fine if this "detection" isn't showed on startups. Pretty annoying bug, just on the last installation step. Any suggestions? Thanks Cipriani My guess is that this may be related to
Wayne: The last log you attached shows that it's running RadRails 0.9.2.6172, which means it's 99.9% likely that you're actually running into
Luis: Which version of RadRails are you running? Thanks for the pointer to
Hi, sorry, but I had installed RadRails yesterday directly from the website and after the bug I uninstalled everything. I don't remember the version.
The good news is: today I installed the version RadRails 0.9.1.200711131528NGT (version installed by Aptana update manager) with AptanaStudio 1.0.0.00002 and everything is fine. After install, however, radRails didn't detect my ruby install (in usr/bin/) but I was able to select without problem (using the dialog) and I created a rails project successfully. If this info above isn't enough, I'm available for any tests needed to solve this bug. Seems resolved for me: as part of efforts to resolve my pro-update login issues I ended up completely re-installing eclipse, aptana, radrails - and now this issue has gone away. Aptana/RDT correctly finds /usr/bin /ruby on my Fedora 8/Sun JVM 1.6.0_0/Ruby 1.8.6 with AS Pro Version: 1.1.10.200712051732, RDT/RadRails 0.9.3.6479 (I think this is a step back from 0.9.9, but I'm not sure ... my box is set up nightly updates and 'compatible' mode so it should be whatever is most-recent, but the 0.9.3 < 0.9.9 )
Marking as resolved. I think this was really a dupe of the gem deadlock issue on the other ticket.
This is fixed in 0.9.3 and also in trunk (so when nightlies are back up, it's fixed there). |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
 |
Bug
Resolved
Critical
'unable to detect ruby' => hang
