NB 6.1 beta - Indexing stops always at the same place

View: New views
6 Messages — Rating Filter:   Alert me  

NB 6.1 beta - Indexing stops always at the same place

by szimek :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I've got Rails project and indexing my functional tests always stops at 83% of some file (not sure which - the path is truncated). Is there somewhere a netbeans log file, where I can see what's wrong?

Re: NB 6.1 beta - Indexing stops always at the same place

by Tor Norbye :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Szimek,
does this happen repeatedly, or just once in a while? There has been a  
bug like that that happens very rarely, and I've never been able to  
reproduce it. If you can, that would be great - I should add some  
logging to see what's going on when this happens.

By the way, the place to look for problems would be the log file -  
View > IDE Log File.

-- Tor

On Mar 13, 2008, at 2:01 PM, szimek wrote:

>
> Hi,
>
> I've got Rails project and indexing my functional tests always stops  
> at 83%
> of some file (not sure which - the path is truncated). Is there  
> somewhere a
> netbeans log file, where I can see what's wrong?
> --
> View this message in context: http://www.nabble.com/NB-6.1-beta---Indexing-stops-always-at-the-same-place-tp16038425p16038425.html
> Sent from the NetBeans Ruby - Users mailing list archive at  
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: NB 6.1 beta - Indexing stops always at the same place

by szimek :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Tor Norbye wrote:
Hi Szimek,
does this happen repeatedly, or just once in a while? There has been a  
bug like that that happens very rarely, and I've never been able to  
reproduce it. If you can, that would be great - I should add some  
logging to see what's going on when this happens.

By the way, the place to look for problems would be the log file -  
View > IDE Log File.

-- Tor

On Mar 13, 2008, at 2:01 PM, szimek wrote:

>
> Hi,
>
> I've got Rails project and indexing my functional tests always stops  
> at 83%
> of some file (not sure which - the path is truncated). Is there  
> somewhere a
> netbeans log file, where I can see what's wrong?
> --
> View this message in context: http://www.nabble.com/NB-6.1-beta---Indexing-stops-always-at-the-same-place-tp16038425p16038425.html
> Sent from the NetBeans Ruby - Users mailing list archive at  
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@ruby.netbeans.org
> For additional commands, e-mail: users-help@ruby.netbeans.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@ruby.netbeans.org
For additional commands, e-mail: users-help@ruby.netbeans.org
Hi Tor,

seems to be happening every time. I've checked the log and can't see any errors there. Lots of warnings, but no errors.

Tried running NB 6.0.1 and it indexes the same project correctly.

Re: NB 6.1 beta - Indexing stops always at the same place

by Tor Norbye :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Mar 13, 2008, at 4:10 PM, szimek wrote:
> Hi Tor,
>
> seems to be happening every time. I've checked the log and can't see  
> any
> errors there. Lots of warnings, but no errors.

Excellent! I've sprinkled logging over the relevant code;  can you  
grab a new build (#1058 or later; see for example
    http://deadlock.netbeans.org/hudson/job/trunk/1058/artifact/nbbuild/dist/zip/
and get one of the distros in there - such as the Ruby only one;  
netbeans-hudson-trunk-1058-ruby.zip  - unzip and then run netbeans/bin/
netbeans)

Important: Invoke it with this flag:

  -J-Druby.indexerbug.level=300

to enable the probe for this specific bug, and then, assuming you  
reproduced the problem again with logging enabled, mail me log file.  
It's in your userdir (whose location is displayed in the About box):

${userdir}/var/log/messages.log

If we're lucky, this will pinpoint the problem. If not, it should at  
least point out where additional information is needed. I'm crossing  
my fingers that you'll still be able to reproduce this with logging  
enabled since this is a bug that's been with us for a while but nobody  
has been able to get it two times in a row.

-- Tor


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: NB 6.1 beta - Indexing stops always at the same place

by szimek :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'll check it on Monday or Sunday evening and let you know.

Re: NB 6.1 beta - Indexing stops always at the same place

by szimek :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Sorry, but it didn't work.

I ran NB Ruby build #1111 and opened project where it was failing, but indexing finished correctly.

I opened NB Ruby beta 1 and it failed where it was always failing. However I got 2 projects opened in this NB instance, so I closed the other one, restarted NB and the indexing went fine this time. I opened the closed project again, restarted NB again and it finished correctly...

I opened this second project in build #1111, restarted NB and indexing also finished correctly.

So the result is that I  can't reproduce this problem on NB beta 1 anymore... Sorry.


BTW. NB build #1111 got updated with newer version of a something-macro module and now I get this error every time I start NB:

java.lang.NoClassDefFoundError: org/netbeans/modules/editor/lib/KitsTracker
at
org.netbeans.modules.editor.macros.Installer$MacrosSettingsInitializer.collectMacroActions(Installer.java:125

but I guess that's normal with dev builds.