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 232401 - SVN wrongly includes parent directory of a project for checking
Summary: SVN wrongly includes parent directory of a project for checking
Status: RESOLVED FIXED
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Subversion (show other bugs)
Version: 7.4
Hardware: PC Mac OS X
: P3 normal (vote)
Assignee: Ondrej Vrabec
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-08 17:12 UTC by host
Modified: 2013-07-11 04:13 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Messages Log (51.29 KB, application/octet-stream)
2013-07-08 17:12 UTC, host
Details

Note You need to log in before you can comment on or make changes to this bug.
Description host 2013-07-08 17:12:04 UTC
Created attachment 136831 [details]
Messages Log

I have the WebApp project "ObTiMA" located under "/Users/holger/Development/ObTiMA" open in NetBeans. For this project I am using SVN 1.8 and the CLI is set in the preferences.

I also have an old copy of the above which is still SVN 1.7 under "/Users/holger/Development/ObTiMA-new". This project is NOT open in NetBeans (and also has not been open after a clean NetBeans install with fresh user and cache directory).

Now, when looking at the messages.log file, I can see the message that:

INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: E155036: Please see the 'svn upgrade' command"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: E155036: The working copy at '/Users/holger/Development/ObTiMA-new'"

So the SVN seems to incorrectly check this later directory ("ObTiMA-new") as well albeit it should only be looking into the former directory ("ObTiMA"). 

(This time I did not forget to attach the messages.log... :-))
Comment 1 host 2013-07-08 17:14:02 UTC
I forgot to say/ask: Might it be that SVN does not start its checking at
"/Users/holger/Development/ObTiMA" but wrongly already at
"/Users/holger/Development" instead?
Comment 2 Ondrej Vrabec 2013-07-08 17:19:30 UTC
Are you sure the cache dir (/Users/holger/Library/Caches/NetBeans/dev) was empty? Did you manually delete it? Subversion cache (/Users/holger/Library/Caches/NetBeans/dev/svncache) keeps traces of opened files/folders almost indefinitely, so unless it was manually deleted/emptied the svn support will always touch the old working copy. Can you try (just to be sure) to run with --userdir EMPTY_FOLDER, open the new project and check the log again?

> Might it be that SVN does not start its checking at
> "/Users/holger/Development/ObTiMA" but wrongly already at
> "/Users/holger/Development" instead?
Maybe, i'll check tomorrow.
Comment 3 host 2013-07-08 17:27:05 UTC
I have closed NetBeans and actually deleted the whole content under "/Users/holger/Library/Caches/NetBeans".

Then I get an even "funnier" error in the messages.log:

INFO [org.netbeans.modules.subversion.FileStatusCache]: FileStatusCache.refreshTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete indexing of 125 binary roots took: 90.570 ms
INFO [org.netbeans.modules.subversion.FileStatusCache]: FileStatusCache.refreshTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion.FileStatusCache]: FileStatusCache.refreshTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion.FileStatusCache]: FileStatusCache.refreshTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion.FileStatusCache]: FileStatusCache.refreshTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion.FileStatusCache]: FileStatusCache.refreshTask: Scanning in progress, trying again in 10.000ms
log4j:WARN No appenders could be found for logger (nu.validator.source.LocationRecorder).
log4j:WARN Please initialize the log4j system properly.
INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion.FileStatusCache]: FileStatusCache.refreshTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: E155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: Subversion.cleanupTask: Scanning in progress, trying again in 10.000ms
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: E155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: warning: W155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: E155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: warning: W155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: E155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: warning: W155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: E155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: warning: W155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: E155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: warning: W155007: '/Users/holger' is not a working copy"
INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: E155007: '/Users/holger' is not a working copy"
...
...
...
Comment 4 Ondrej Vrabec 2013-07-08 17:43:07 UTC
... and any trace of '/Users/holger/Development/ObTiMA-new' ?

> INFO [org.netbeans.modules.subversion]: cli: ERROR "svn: E155007:
> '/Users/holger' is not a working copy"
that's probably OK.
Comment 5 host 2013-07-08 18:56:26 UTC
No, in the later messages.log there is indeed no trace anymore of "ObTiMA-new". So perhaps (or probably) I am wrong but I noticed one thing:

Before the deletion of the cache, when I was trying to update the project at "/Users/holger/Development/ObTiMA" then SVN was also accessing "/Users/holger/Development/ObTiMA-new". Thus SVN seemingly started to work at the level of "/Users/holger/Development".

And now, after deleting the whole NetBeans cache directory, SVN seems to start to work again one level higher at "/Users/holger". 

(BTW: I cut off the "E155007" error messages. There were actually many more lines with that error message.)
Comment 6 Ondrej Vrabec 2013-07-08 19:06:32 UTC
It's quite the opposite, it starts deep within the files tree and traverses to the root, so it ends at /Users/holger/Development (or /Users/holger maybe). However i will take a look and check if that's actually a problem or can be avoided.
Comment 7 Ondrej Vrabec 2013-07-09 12:05:09 UTC
Happens with CLI when asked for status of metadata folder, trying to avoid that.

fix: http://hg.netbeans.org/core-main/rev/0d6f7683bcf8
Comment 8 Quality Engineering 2013-07-11 04:13:04 UTC
Integrated into 'main-silver', will be available in build *201307102300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/0d6f7683bcf8
User: Ondrej Vrabec <ovrabec@netbeans.org>
Log: #232401 - SVN wrongly includes parent directory of a project for checking
svn status is eventually called on current working directory when asked for .svn folder's status because commandline client skips such target from the command