This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 152761 - [65cat] No longer able to find new or updated gems
Summary: [65cat] No longer able to find new or updated gems
Status: RESOLVED WORKSFORME
Alias: None
Product: ruby
Classification: Unclassified
Component: Gems (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Martin Krauskopf
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2008-11-08 07:11 UTC by esmithbss
Modified: 2009-02-19 23:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Log file with default settings. (57.53 KB, text/plain)
2008-11-08 07:13 UTC, esmithbss
Details

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2008-11-08 07:11:47 UTC
[ BUILD # : RC-2 ]
[ JDK VERSION : 1.6.0_07 ]

Under RC-2 with no proxies, if you bring up the ruby gems dialog box
for the built-in JRuby 1.1.4 platform, then attempt to refresh the
list of gems, the system is unable to identify any gems for the "New
Gems" or "Updated" pages.

There are many gems that aren't installed, and there's an update for
Rails to 2.1.4  that is not displayed.
Comment 1 esmithbss 2008-11-08 07:13:17 UTC
Created attachment 73531 [details]
Log file with default settings.
Comment 2 esmithbss 2008-11-08 07:19:47 UTC
The updating operation fails when the default settings are used for NetBeans; however, if the additional Ruby Logging
command line options are added to the system, the commands succeed.

Comment 3 Martin Krauskopf 2008-11-10 13:13:37 UTC
Hi, I've try to run 6.5 RC2 (without logging switches), went to Gem Manager and saw there 8 updates for bundled in
JRuby-1.1.4. Also after pressing 'Reload Gems' they were shown again correctly. Update of them succeed (just linecache
native extension failed).

Could that be just some rubyforge.org outage or something similar? Or are the problems permanent. BTW the older 2.1.x
release of Rails seems to be 2.1.2 on RubyForge. Are you using some alternate source?
Comment 4 esmithbss 2008-11-10 20:06:09 UTC
I can see an outage as a possibility; however, if there is an outage, then wouldn't it be a communications failure and
result in an exception message "Failed to connect...."

When I initially encountered this problem it existed for clean and dirty user directories and lasted from my initial
installation of RC-2 through setting the extra logging flags (roughly 10 hours); however, since I added the flags, even
removing them and using a clean user dir doesn't allow me to reproduce the error, I am marking this Resolved "Works For Me"

I will file an E.R. for the error message.
Comment 5 Martin Krauskopf 2008-11-11 11:21:47 UTC
There should be already the error dialog. More in the issue 152900 you've filed.